Blago's Burst-Miner (Win)
-
hi guys,
ive been having my miner crash over night for the past few days. with the following in the logs. just wondering if theres a bug that causes this to happen.
this is the line just before it bombed out to desktop
12:29:18 * GMI: Sent: POST /burst?requestType=getMiningInfo HTTP/1.0\r\nHost: burst.lexitoshi.uk:8124\r\nContent-Length: 0\r\nConnection: close\r\n\r\n 12:29:18 * GMI: Received: HTTP/1.1 200 OK\r\nDate: Wed, 21 Jun 2017 11:29:20 GMT\r\nConnection: close\r\n\r\n{"requestProcessingTime":0,"baseTarget":"404996","height":"373452","generationSignature":"a4dadfda2d8924685e25cf44f39c5468953077029281271705da3ae91251cc9b","targetDeadline":2592000} 12:29:20 * GMI: Sent: POST /burst?requestType=getMiningInfo HTTP/1.0\r\nHost: burst.lexitoshi.uk:8124\r\nContent-Length: 0\r\nConnection: close\r\n\r\n 12:29:20 * GMI: Received: HTTP/1.1 200 OK\r\nDate: Wed, 21 Jun 2017 11:29:21 GMT\r\nConnection: close\r\n\r\n{"generationSignature":"b7615ccc7868c42ae64f16232719828cb0848249cbc22d562f4617dfcb117df9","baseTarget":"434512","requestProcessingTime":0,"height":"373453","targetDeadline":2592000} 12:29:21 realloc: 1023 12:29:21 realloc: 1352 12:29:21 realloc: 1420it could be from the show winner part of the application. which makes me think why do we have this feature in.
700 miners. trying to get the winner all from the same wallet servers each block is a bit excessive. and will probably get worse as time goes on.
-
@Lexicon said in Blago's Burst-Miner (Win):
Hi guys, - I've been having my miner crash over night for the past few days. with the following in the logs. just wondering if theres a bug that causes this to happen. It could be from the show winner part of the application. which makes me think why do we have this feature in. > 700 miners. trying to get the winner all from the same wallet servers each block is a bit excessive. and will probably get worse as time goes on.
When the Block Winner (quite frequently) can't be located, I just get an error message, no crash.
WINNER: Connect function failed with error: 10060Also, can you not just comment-out the winner-polling command lines from your config file?
Eg. (For the Blago Miner), remove: InfoAddr & InfoPort.
-
@BeholdMiNuggets i get the same however at a random point during the night the miner will crash to desktop. ive removed the lines from my config for now but its better to fix issues than to leave a bug that could potentially wipe out someones miner for a night.
when i say crash. the screen greys out and it says this process has stopped responding. every time its after those 2-3 lines in the logs realloc: ####
also this isnt mentioning that every single miner will be querying the same web wallets on block start.
now lets say we have 13000 miners. each doing 2 api calls to a wallet when the round starts. that 26,000 api calls. in just a few seconds. at the rate at which burst is getting noticed. this will get bigger and bigger.
-
@Lexicon Is the realloc statement coming from the miner, or Java itself - possible memory leak issue ?
-
@haitch its coming from the miner from the looks of it. ive got a few others reporting their miner crashing as well with same issues im facing. lol so i turned on logging and i cant see any other instances where realloc appears except when it crashs
-
@Lexicon Yeah, it looks like it's from the miner - but I've never seen it. Possibly you need tweaks to java memory allocation ? -xmx and -xms ?
-
This post is deleted!
-
Which unit of time does "TargetDeadline" use?
-
@Akito seconds
-
This is the miner that is inside of the burst wallet 0.3.9.7 correct?
-
@sevencardz Carrizo amd and ryzen chips do indeed have avx2
-
I can also confirm that the min er crashes at night.
Any solutions available?
-
This post is deleted!
-
@Lorby if you use v1.170601 at v3 ninja pools - miner will crash (pools bug).
update to v1.170603 https://github.com/Blagodarenko/miner-burst/releases/tag/v1.170603
-
@Blago Hey I'm new to mining and I was tinkering with the settings on your miner today trying to find out what the commands do and all of a sudden a message appeared in the miner that said something like "Recommended size for this block is 6978GB" how did I make that message appear and what does it mean. Does it somehow calculate this from the current difficulty or something? Would be interesting to see how the recommendation changes with increase in difficulty. I was mining on lex at the time in case that is of importance.
Thanks in advance, Wes :)
-
@Weswyn if you hit 'r' key - miner will show "Recommended size" for current block at that pool.
If you have "Recommended size" plots - you will get minimum 1 deadline for block (avg)

