@claymore:
1) Maybe I found a hint: Is it possible that it is some kind of IP address caching issue? It seems to happen to rigs which reboot and get another (dynamic) IP address. If I change the "IP" field in EthMan to the current numeric IP address or use an alternative DNS name which resolves to the same computer EthMan shows correct "up" state. If I change it to the old one its shown "down" again. Restarting EthMan seems to update these values and the rig ist shown online, even with the same old name ("IP" entry). Or it is some kind of update process which is only executed when adding/changing a rig entry. But maybe this helps...
2) Did you read my comment about retriggering above and understand my issue?
Please test this version:
https://mega.nz/#!C5xiUSYY!QY44OAExh5EQ2elGcH1DvfbkQMTkgMSwOEMLoG0lUCULet me know if you still have the issue.
DNS caching can cause some additional delays, but in a minute the lost rig must be found anyway.
I will add retriggering in next update.
Need advice from Mister Claymore or someone else.
I'm mining now at ethermine.org (Europe (France): eu1.ethermine.org:4444)
The pool uses diff 40M
My 3-4 cards rigs are doing fine, but I have 2 standalone comps with only one 30mhs card in each. And this one-card rigs have huge (5-15%) stale share rate reported by pool. all rigs have identical and fast Internet access with the multi-card rigs, 70-100ms latency to pool. Is it due to high pool diff and low (30mhs) rig speed? Is there a way to fix this without changing a pool? I can't move this cards to multi-card rigs ((
I'm using latest Claymore 9.5 but older versions seem to behave the same.
Thanx in advance
40M? May be 4000M? Stale shares can be caused by delays in new job broadcasts from pool side if the pool sends new jobs to faster miners firstly. Though it's just an idea.