I've had a bit of an issue the last couple of days and I'm hoping to nip it in the bud...
On Wednesday, I switched to p2pool on a local node and switched it into my #1 position. Hashing seemed to be going OK but on Thursday in the day, I noticed my miner was no longer reachable (no ping, my router showed that port as not connected). Checking the p2pool graph showed that the miner had stopped hashing at
6am. I had someone at home restart it and hashing continued. However, p2pool was adversely affecting my internet connection so I shut it down, allowing the miner to fall back to antpool. I checked it was hashing on the pool and thought no more of it.
This morning, I was woken by a beeping sound at
6am. Could this be a recurring problem? Has anyone heard of this before? It just seems odd that the times are the same.
A few more relevant details:
- Other than this, the miner has been hashing for over a week with no issues.
- p2pool was not running this morning so it should have just been failing to connect and falling back to antpool
- Miner did not seem especially hot this morning
- I moved the miner yesterday evening to a different room so it should not be location dependent. The new area should actually be cooler (currently running at 52 and 45).
- Not sure of the firmware version but kernel is 3.8.13 and cgminer is 4.8.0, Hardware is 3.4.3.0
So just a coincidence or something else?