Network would be different as well. Might be useful to do some analyzing of connection latency as well. I'm not sure how the A4 work but perhaps if it thinks there is network issues it reboots as well?
Yes, check the 'Get Failures' stats for Getwork failures first, and then look at Pool Rejects for high Pool stales.
Think I figured it out.
Had to SSH into the PI and clear the tmp directory which contained a cgminer.lock file
Once I cleared that, it appears to be running normally again... almost
10 30 mins now without a reboot and prior it would reboot around 5 minutes like clock work.
Owners of the A4, I recommend you take note of this because if it happened to me, its bound to happen to you
-- All I did was power it off and move it.
Questions:
1. what is the function of cgminer.lock?
2. what event possible triggers occurrence this cgminer.lock?
3. do we need to clear tmp directory regularly?
Best I can tell it's a temp file that gets created that contains information while the miner is running.
From my research, when the raspberry pi reboots, its supposed to clear the tmp directory. However when you just flip the power switch and shut it off, the Pi doesn't have the opportunity to clear this file. I only recommend doing this if you're having issues getting your A4 to mine or if its in a 5 minute reboot loop like mine was.
I took a guess and manually cleared the file/directory by performing the following steps.
1. Make SURE the miner is stopped (note: I had issues with the thing starting itself up even with Manual Start configured)
2. SSH Into the Pi
3. Navigate to tmp directory in the root
4. Clear contents of tmp directory with command
5. Restart the miner
I observed this file was re-created when the miner started again.
Over 16 hours now since I did this and its working fine again.
If you notice I also set the time/date correctly on the Pi finally so that's accurate in this screen capture.
Update on this, ran fine for 3 days then yesterday around 5am this problem started again. I didn't catch it until today. I again deleted the cgminer.lock file and rebooted the pi manually as mentioned above and it seems to have corrected the problem for now...
Lost 24 hours of mining because I wasn't watching it...
I guess next step is to take another copy of 2.0.2 on an SD card and go swap it out.
Anyone know of a good way of changing the default IP address without a 2nd Pi to change it from? I can see the necessary files in the image but can't find a successful method of editing it from Windows... maybe it can be done from Linux?
Another Update.
So after about 2-3 Hours of working normally after this post, the A4 went down again and started boot looping every 5 mins or so. I didn't have opportunity to check on it overnight and the next morning I found it completely offline and the Pi unable to be reached via ping, ssh, or accessible via web interface.
I power-cycled the entire unit and it came back online normally. Within 5 minutes, it rebooted again. I got the A4 back up and stopped mining. I changed the speed to 1000mhz and started it mining, rebooted again within 5 mins.
I want to stress this is the Pi rebooting for what appears to be a script going off, the A4 appears to be hashing normally when it happens.
I reapplied all the settings, set everything to 1200mhz, typed back in my pool information, added a 3rd pool and started mining again.
Now its be running for over 9 hours on PH without an issue.
I've got new SD cards coming today and I'm going to replace the one in the Pi with a fresh 2.0.2 image/sd card the next time it goes down again.
I'm fairly certain at this point that I have not seen the end of this issue.
I reached out to Inno for assistance in steps I can take if this issue persists after I replace the SD Card / Image.