Quote from: shakes1118 on February 12, 2018, 01:05:41 AM

Quote from: ltc_bilic on February 11, 2018, 07:40:29 PM

@realbminer

Today there was a problem with the zenmine.pro mining pool,...don't know what was up but after investigating I've found out that bminer still has some sort of connection problems...see the picture below,...all this time the GPU was at full load,...although it didn't had a proper connection to the pool and I couldn't see it on the minning pool. Then I've switched to ewbf/dstm, both miners connected immediately and are working properly? Huh

I use following in a batch file:

Code:

-max-temperature 80 -max-network-failures 5 -gpucheck 0 -watchdog=false

...

This is a huge issue! I've lost at least half of the hashrate because of this bug.

Why are you using 'max-network-failures 5' & 'watchdog=false'? Shouldn't you leave it at the default so it will continue to try to recover the connection, especially if you are complaining of a bug saying it's not connecting?

The documentation on bminer.me states:

Quote

-max-network-failures Default: -1 Description: Number of consecutive attempts that Bminer tries to recover from network failures. Set to -1 to keep on recovering.
-watchdog Default: true Description: Automatic restart to recover from hung GPUs. Bminer exits itself in case of errors if watchdog is disabled.

I've already tested this, you can read it in message if you read it properly unfortunately it still doesn't work. I have to use watchdog=false because on systems with 8+ gpus you cannot run this miner properly, because the cpu usage in the beginning is too high - first 2-4 min that the miner needs to initialize it self to max speed,...then the cpu lowers to normal state 40-60% on low cost G3930. I've reported this bug already and few others too.

Now what's even more bizarre regarding this connectivity issue:
- yesterday: half of the mining farm was still working with bminer properly, the other half still had connection issues, so i switched back to ewbf with problematic rigs
- today: even the other half couldn't connect,...so switching back to ewbf/dstm permanently until this issue is properly addressed.