http://

Quote from: xPETEx on March 19, 2018, 02:26:34 AM

Quote from: jmacodex on March 19, 2018, 01:18:36 AM

Quote from: xPETEx on March 18, 2018, 06:14:56 PM

Quote from: write2garg on March 18, 2018, 04:40:39 AM

Quote from: dzap on March 18, 2018, 12:18:25 AM

the log on the dashboard containing like 5 last reboot reasons would be great. As logging locally just corrupts usb flash memory within a week or two, already gone through that couple of times...

after claymore 11.0 , my rig are restarting every few hours, i am unable to understand the problem so till now i am using claymore 11.0, plz do some for your customers...

SSH into your rig. When it reboots the SSH session will end, but whatever happened to cause the crash will still be displayed. Very easy/fast way to troubleshoot. likely you have a card overclocked too high for the new Claymore improvements in 11.3+

"SSH session will end, but whatever happened to cause the crash will still be displayed" this means monitoring the rig like 24/7 with a display, this defeats the purpose of SMOS, the point of the log is to check what happened after several hours/days in operation because after a day or two my rig has restarted already a couple of hours ago.

would like also to ask (not so technical person), is the SSH in PuTTY any different from direct SSH?

If you want to dig through the log you can also do that. The log is there, just SSH into the miner and pull it up. The way I suggested is much more efficient use of your time. You don't need 24/7 monitoring. Just run it on your personal computer, and when the miner reboots you'll see the cause in PuTTY whenever you're back at your personal computer. Do this for a couple days until you eliminate the cause of your reboots.

As you said, the miner reboots a couple times and hours before you get to look into it. Digging through logs will take hours of your time to scroll back to try and find the crashes. My suggestion will put the cause of the crash immediately in front of you with minimal effort.

To answer your question, PuTTY works well as an SSH client on Windows. If you hover over your rig's name in SMOS you'll see the ip address of the rig. log into that address with PuTTY. username: "miner", password "miner". once you log into it type "screen -x miner" and you'll pull up the miner screen. let it run until the miner reboots/crashes. when it crashes you'll get a pop-up in PuTTY that the connection disconnected, but you'll be able to see what caused the drop.

i've been using putty "screen -x miner" since I use SMOS, it is also in the help section.

like just now, one of my rig stopped, and screen can only show the hash rate has dropped to 8Mhs across all 6GPUs..
"Digging through logs will take hours of your time" SMOS is designed for a farm setup, so it will be impractical to dig all of your rig.
having a log that show only what caused the crash will help, we are not asking for the whole log, we are only interested what caused the crash.