Quote from: papampi on May 01, 2018, 06:57:03 PM

Quote from: urnzwy on May 01, 2018, 03:06:40 PM

Quote from: papampi on May 01, 2018, 06:11:45 AM

Quote from: urnzwy on May 01, 2018, 05:52:20 AM

Error on rig 2 - Two different rigs, crashing within a minute of each other. Tell me that isn't weird.

tail -f /home/m1/nvoc_logs/watchdog-screenlog.0
m1@m1-desktop:~$ tail -f /home/m1/nvoc_logs/watchdog-screenlog.0
Watchdog for nvOC v0019-2.0 - Community Release
Version: v0019-2.0.011

LOG FILE: (Showing the last 10 recorded entries)
| 12 | 120W | 3.42 Sol/W |
+-----+-------------+--------------+
INFO 09:34:50: GPU3 Accepted share 186ms [A:454, R:1]
INFO 09:34:51: GPU7 Accepted share 187ms [A:477, R:1]
CRITICAL: Sun Apr 29 09:35:17 MST 2018 - GPU Utilization is too low: restarting 3main...
Mon Apr 30 22:35:29 MST 2018 - Lost GPU so restarting system. Found GPU's:
Unable to determine the device handle for GPU 0000:0F:00.0: GPU is lost. Reboot the system to recover this GPU

Mon Apr 30 22:35:30 MST 2018 - reboot in 10 seconds

If both rigs crash and freeze at the same time, it can be electrical problem
I had almost same issue a while back and some of my rigs were crashing all at the same time,
found out when one of the room venting fans was turning on it was making a high frequency noise in electricity and 3-4 rigs gets the lost gpu at the same time and reboot.
After a month of pulling my hairs to find the problem I changed that fan and problem solved.

Open 5watchdog
Change:

Code:

echo "$(date) - Lost GPU so restarting system. Found GPU's:" | tee -a ${LOG_FILE}

To:

Code:

echo "$(date) - Lost GPU $GPU so restarting system. Found GPU's:" | tee -a ${LOG_FILE}

So you can check GPU number that is lost, then check if it is the same GPU always get lost?
If its always the same GPU, remove it from the rig and check, may be a faulty GPU, riser or power cable.
If after removing the GPU, the problem jumps to another GPU then it could be a power problem.

Hmmmm interesting about the electrical issue. I have two 8" hyperfans used as exhaust fans that run 100% 24/7. But could be a possibility.

Last night I recompiled the miners again, set the max fan limit to 90 from another one of your posts and set the power restore to 80 and changed EWBF to 3_3 from 3_4.

I will try this for a day and see if anything happens. It's just so strange that on Hush, it worked completely fine.

I had this kinda happen before and it was the mining server "disconnecting". Switched pools and all was good.

Any way to make watchdog wait an extended period of time for error's to clear themselves before trying to restart 3main?

Also, do the miners themselves if watch dog is disabled keep a max temp limit? I notice when starting EWBF it says max temp 90*. While I don't want temps that high, if it keeps the miner going and safe then I will consider it.

I have two 20 inches fans with a thermostat that start them when room temp goes above 15C and stop at 10C, and one of them causing problem at startup.
Anyway, I suggest you try out dstm zm miner, much better in my experience.
What are your PSUs? and how much you draw from them? and what about riser powers?

If both rigs restart 3main at same time when mining some coins and all is good with other coin try to change the pool.
Recently I'm getting lots of pool disconnect from MPH and all rigs restart 3main almost at same time.

I have two 1600W server PSU's for the cards (6 on each) one 850W EVGA ATX with one card / riser.

All using 6-8pin, risers are split once (1 cable per 2 risers)

Any chance it's a memory issue? I am running 4GB, my memory says 3.2GB / 4GB in use (85%).

Since disabling watchdog, it shouldn't be a server issue. The miner would just keep trying to reconnect.