Quote from: peterboy1 on November 09, 2018, 11:00:45 AM

Quote from: todxx on November 09, 2018, 10:54:56 AM

Quote from: peterboy1 on November 09, 2018, 08:24:54 AM

i encountered a problem today. my pool emailed me that one of my rig isnt working. so after an hour, i checked it. its hashing at 0 for the whole hour.

upon backreading the console, i saw "pool x.x.x.x was closed due to an error", then the hash became 0 and never attempted to reconnect.

whats up?

Well that's not what it's supposed to do. It should continue to attempt to reconnect to the pool until it succeeds.
So after this error, the miner did not attempt to connect to the pool at all? Were there any messages printed about the pool after that point?

nothing after that. just the regular hashes print, which shows my current hashrate at that time 0.

oh, if this will help, im using nicehash.

The pool used shouldn't make a difference, but I also don't know why this would be happening either. I'll run against nicehash and see if I can get one of my rigs into the same situation.