Rig stuck in DNS resolve problem... about nvoc_by_fullzero_community_release HOT 6 CLOSED

I can attest to this being the case for several hundred of rigs, and its a documented ubuntu bug. I will come back with the bug bulletin shortly.

from nvoc_by_fullzero_community_release.

So It was weird,
Network had more problems last night and only those same 5 rigs was showing that symptom.
Added "-minspeed 50" to claymore opts so it restart miner if hash was low
No idea what is the problem.

from nvoc_by_fullzero_community_release.

No ideas about that, The error may be thrown if you setup a DNS server which is remote (eg. google's 8.8.8.8). Does restarting a single miner on one rig solved the problem of all 5 rigs or you needed to restart all of them?

from nvoc_by_fullzero_community_release.

All the rigs are almost identical and with static IP.
Just checked /etc/resolvconf/resolv.conf.d/base and only 1 rig has nameservers set in it, all others including those 5 are empty.

At first occurrence I restarted miners with killing watchdog and 3main, but when it happened again, I just killed miner on one rig and waited, after 10-15 seconds watchdog was able to resolve google address and goes for internet is up, checked miner not running and started it.
Waited for other rigs a while, but had to kill all other miners and their watchdogs start resolving address and starting miners.

from nvoc_by_fullzero_community_release.

I have 15 rigs, and only 5 showing this problem.

from nvoc_by_fullzero_community_release.

The workaround is now available from #116

from nvoc_by_fullzero_community_release.