Release 1.5.2 is fantastic! I've been running it for a little over a week now, and it's been rock solid. Thank you again!
RatPatrol
@RatPatrol
Posts made by RatPatrol
-
RE: creepMiner - C++ Burst Miner (based on Uray's Miner)posted in Miner
-
RE: Cannot connect to pool.burstcoin.biz?posted in Help & Support
@rnahlawi I can access the pool's web page and watch the activity, and the miner does know when a new round starts as it will read drives with each new round.
@haitch Good to know about the IPs being not pingable. I was beginning to wonder whether or not I wound up banned for some reason. :-)
I reverted back to creepMiner 1.4.3, and it's working fine again.
-
Cannot connect to pool.burstcoin.biz?posted in Help & Support
I've been mining at burstcoin.biz for several days using creepMiner 1.4.6 on Ubuntu 16.04. For the most part, it's been problem free.
Today, out of the blue, I've run into an issue where creepMiner will begin reading the drives at the beginning of each round, but no DLs are being submitted, and I'm not getting any winner info either. Additionally, the read process stops at 90% and stays there until the beginning of the next round.
Looking in the log files, I found a couple of errors:
04.03.2017 05:27:25 (12, src/Wallet.cpp, 54, Debug): Could not get last winner! 04.03.2017 05:27:25 (12, src/Request.cpp, 46, Error): Error on sending request: Connection refused 04.03.2017 05:27:25 (12, src/Request.cpp, 47, Error): Stackframe Miner::runGetLastWinner (in "src/MinerData.cpp", line 225) Wallet::getWinnerOfBlock (in "src/Wallet.cpp", line 30) Wallet::sendWalletRequest (in "src/Wallet.cpp", line 155) Request::send(Poco::Net::HTTPRequest&) (in "src/Request.cpp", line 35)04.03.2017 05:27:30 (8, src/Wallet.cpp, 83, Debug): Could not get name of account!I've tried pinging 216.165.179.42 and even 216.165.179.44, but I get no response from either address.
Any ideas as to what the problem might be?
-
RE: creepMiner - C++ Burst Miner (based on Uray's Miner)posted in Miner
@Creepsky Got it. Thank you for the explanation!
-
RE: creepMiner - C++ Burst Miner (based on Uray's Miner)posted in Miner
@Creepsky No worries.
Thanks for the tip on changing the mining intensity. Setting it to '1' brought the read times close to what I was seeing originally. Because I don't fully understand what the verifiers do, am I compromising my reads by running at a lower number?
-
RE: creepMiner - C++ Burst Miner (based on Uray's Miner)posted in Miner
@Creepsky It's been running for over 24 hours, and that issue has not popped up again. I also like how it simply displays eligible DLs.
One thing I have noticed is that the read times have roughly doubled with this latest version:
I've tried changing a couple of settings in the config file....mainly buffer size and plot readers, but it seemed to have little to no effect on the read times. I'll keep playing with the settings and see if I can get an increase.
-
RE: creepMiner - C++ Burst Miner (based on Uray's Miner)posted in Miner
@Creepsky Thank you! I'll give it a try and report back.
Thank you again for your work on this.
-
RE: creepMiner - C++ Burst Miner (based on Uray's Miner)posted in Miner
Thank you for your work on developing this.
I'm running the latest build under Ubuntu 16.04, and I keep running into a situation where after an hour or so of running fine, it stops scanning the drives and submitting deadlines. System is rather old - dual 4-core Intel QX9775 and 16GB of RAM. This has happened with two different pools:
Here is the corresponding entries in the log file:
-------------------------------------------------- 26.02.2017 19:24:08 (0, src/Miner.cpp, 175, Debug): Verification queue cleared. 26.02.2017 19:24:08 (0, src/Miner.cpp, 178, Debug): Locking threads... 26.02.2017 19:24:08 (0, src/Miner.cpp, 180, Debug): Threads locked, setting up new block 332450... 26.02.2017 19:24:08 (0, src/Miner.cpp, 283, Notice): -------------------------------------------------- block# 332450 scoop# 1734 baseTarget# 1035051 -------------------------------------------------- 26.02.2017 19:29:02 (0, src/Miner.cpp, 175, Debug): Verification queue cleared. 26.02.2017 19:29:02 (0, src/Miner.cpp, 178, Debug): Locking threads... 26.02.2017 19:29:02 (0, src/Miner.cpp, 180, Debug): Threads locked, setting up new block 332451... 26.02.2017 19:29:02 (0, src/Miner.cpp, 283, Notice): -------------------------------------------------- block# 332451 scoop# 1877 baseTarget# 1079299 -------------------------------------------------- 26.02.2017 19:29:11 (0, src/Miner.cpp, 175, Debug): Verification queue cleared. 26.02.2017 19:29:11 (0, src/Miner.cpp, 178, Debug): Locking threads... 26.02.2017 19:29:11 (0, src/Miner.cpp, 180, Debug): Threads locked, setting up new block 332452... 26.02.2017 19:29:11 (0, src/Miner.cpp, 283, Notice): -------------------------------------------------- block# 332452 scoop# 1781 baseTarget# 1007656 -------------------------------------------------- 26.02.2017 19:31:36 (0, src/Miner.cpp, 175, Debug): Verification queue cleared. 26.02.2017 19:31:36 (0, src/Miner.cpp, 178, Debug): Locking threads... 26.02.2017 19:31:36 (0, src/Miner.cpp, 180, Debug): Threads locked, setting up new block 332453... 26.02.2017 19:31:36 (0, src/Miner.cpp, 283, Notice): -------------------------------------------------- block# 332453 scoop# 2493 baseTarget# 1011097 -------------------------------------------------- 26.02.2017 19:34:07 (0, src/Miner.cpp, 175, Debug): Verification queue cleared. 26.02.2017 19:34:07 (0, src/Miner.cpp, 178, Debug): Locking threads... 26.02.2017 19:34:07 (0, src/Miner.cpp, 180, Debug): Threads locked, setting up new block 332454... 26.02.2017 19:34:07 (0, src/Miner.cpp, 283, Notice): -------------------------------------------------- block# 332454 scoop# 1886 baseTarget# 844649 -------------------------------------------------- 26.02.2017 19:34:08 (0, src/Miner.cpp, 262, Information): -------------------------------------------------- last block winner: block# 332453 winner-numeric 8786871724884427616 winner-address L2V2-AXNC-VW9G-9XBWM -------------------------------------------------- 26.02.2017 19:38:18 (0, src/Miner.cpp, 175, Debug): Verification queue cleared. 26.02.2017 19:38:18 (0, src/Miner.cpp, 178, Debug): Locking threads... 26.02.2017 19:38:18 (0, src/Miner.cpp, 180, Debug): Threads locked, setting up new block 332455... 26.02.2017 19:38:18 (0, src/Miner.cpp, 283, Notice): -------------------------------------------------- block# 332455 scoop# 3151 baseTarget# 869025 -------------------------------------------------- 26.02.2017 19:38:19 (0, src/Miner.cpp, 262, Information): -------------------------------------------------- last block winner: block# 332454 winner-numeric 2173983320505215447 winner-address EUGR-BZ97-JG3W-3CWCW winner-name NeatCrypto --------------------------------------------------My config file:
{ "Start Server" : true, "logging" : { "config" : "information", "general" : "information", "miner" : "information", "nonceSubmitter" : "information", "path" : "", "plotReader" : "information", "plotVerifier" : "information", "server" : "fatal", "session" : "error", "socket" : "off", "wallet" : "information" }, "maxBufferSizeMB" : 4096, "maxPlotReaders" : 0, "miningInfoUrl" : "http:\/\/pool.burstcoin.biz:8124", "miningIntensity" : 3, "output" : { "dirDone" : true, "lastWinner" : true, "nonceConfirmed" : true, "nonceFound" : true, "nonceOnTheWay" : true, "nonceSent" : true, "plotDone" : false }, "passphrase" : { "algorithm" : "aes-256-cbc", "decrypted" : "", "deleteKey" : false, "encrypted" : "", "iterations" : 0, "key" : "", "salt" : "" }, "plots" : [ "\/media\/xxxxx\/New Volume\/plots", "\/media\/xxxxx\/one\/plots", "\/media\/xxxxx\/two\/plots", "\/media\/xxxxx\/three\/plots", "\/media\/xxxxx\/four\/plots", "\/media\/xxxxx\/five\/plots", "\/media\/xxxxx\/six\/plots", "\/media\/xxxxx\/seven\/plots", "\/media\/xxxxx\/eight\/plots", "\/media\/xxxxx\/nine\/plots" ], "poolUrl" : "http:\/\/pool.burstcoin.biz:8124", "serverUrl" : "http:\/\/192.168.0.100:8080", "submissionMaxRetry" : 3, "targetDeadline" : "0y 0m 20d 15:00:00", "timeout" : 45, "walletUrl" : "https:\/\/wallet.burst-team.us:8128"The only thing I can think of is the memory allocation, but System Monitor shows that there is still plenty of unused RAM. Any thoughts?
-
RE: XPlotter for optimized plots (CPU)posted in Plotter
@Blago said in XPlotter for optimized plots (CPU):
@RatPatrol better when nonces_per_thread = multiple by 1024.
In your case try -t 30 -mem 30G (will 2048)
or -t 30 -mem 45G (will 3096)Thanks for the tip. I'll give it a try this weekend.
-
RE: XPlotter for optimized plots (CPU)posted in Plotter
I'm just starting out with Burstcoin and my plan is to mine using 10TB. Right now, I'm plotting simultaneously on two vastly different machines. Both are writing to identical 1TB drives. One is a home-built PC with a 3-core AMD A6-3500 and 8GB of ram:

The other is an HP workstation with dual E5-2670s and 64GB of ram:

Quite a difference. :-D
As others have experienced, the bottleneck on the HP is write speed, and watching that has me wondering about how RAM and threads affect performance.
I get that the amount of RAM allocated to plotting determines the stagger size. So then is the stagger the number of nonces generated per pass ("Generating nonces from xxxxxxx to yyyyyyy")? So the more RAM allocated, the more nonces created per pass? And then the number of threads and processor speed determines how fast nonces are generated?
Thank you blago for your work on this. And thank you to everyone else contributing. I've been digging through the forums for the past few days trying to wrap my head around all this and have found a ton of great info here. I hope to be up and mining by the weekend.


