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?