Hello folks, I am using Claymore 11 and Ethos and am having the following issue:
Random number of rigs are decreasing their hashing to 0 and starting all over again. This is what happens with the reported hashrate to the pool (check the irregular black line - the reported hashrate in the pool in the first two images, the other images are representing the problem in the Ethos remote config file)
https://imgur.com/a/2Zx2fThis was happenning at the beginning during random time (black line in top pool image in the link above), but now (since many tests and restarts) it seems it happens every hour (bottom pool image).
I thought at the beginning that the problem is in the network, but it seems it is not, bacause I made many tests with the network: At the beginning I was using 2 ISPs (with fixed IPs) connected to one dual wan router, after them I connected 2 more routers one after the other, and after that 3 basic 8-port 100 mbps unmanaged switches that connected to the 13 rigs, but now I am using 2 independent networks with 3 rigs on one of the networks and the rest of the rigs on the other network, with direct connection from router to switch. I have changed the 3 switches with one 24 port switch and again I do have this problem every hour.
This problem occured when I upgraded from 8 to 13 rigs at the beginning of February.
I spoke with the folks from Ethos support and explained them all about the network, I told them the brands and models of the network devices that I am using and they said that the devices seems to be ok as quality for 13 rigs network (now 10 rigs network is with dual wan router
https://www.tp-link.com/us/products/details/cat-4909_TL-ER6020.html and
http://www.dlink.com/uk/en/products/des-1024d-24-port-10-100mbps-desktop-switch, before the dual wan router there is one HUAWEI router of the ISP that is configured as a bridge with fixed IP). The Ethos support folks suggested that I update Claymore from 10.2 to 11, but it didn't help. They also suggested that I add this line to the Ethos remote config file:
"claymore=flags -nofee 1" in order to check the if the problem is not in the DNS setting.
As far as I understand from the beginning of this thread, this line disables the dev fee. By putting this line my rigs stabilized but hashed 4% less as it is explained in the 1st post.
Any ideas how to fix this unstability problem?
It seems that this guy from Reddit had similar issue:
https://www.reddit.com/r/EtherMining/comments/6glgii/are_you_using_the_nofee_comm_in_claymore_miner/