In this case, the Cerbo shouldn’t reboot upon network connectivity loss. If it does anyway, the reason may be the watchdog being too sensitive. Check the log files for the reason of the reboot, and if it was the watchdog, increase the threshold to avoid reboots.
VRM/advanced. Create a custom widget using gateway dbus roundtrip time. It gives a general indication of Cerbo loading.
You can also ssh into the Cerbo to check the watchdog file for clues. Add any OS large features that depend on the network? top or htop is another tool used for Cerbo load.
Yes, that’s via SSH. The dbus load in vrm gives an indication about system load. Mine is very high, but with the watchdog parameters set high enough, there are no unwanted reboots.
Check out the thread I’ve linked before for more discussions about the watchdog behavior.
Log files can be viewed via SSH: root@einstein:/var/log# cat messages.0
There are a couple log files in that directory:
root@VictronCerboEinstein:/var/log# ls -l
-rw-r–r-- 1 root root 292 May 15 18:23 lastlog
drwx------ 2 root root 4096 May 15 18:16 localsettings
-rw-r–r-- 1 root root 34681 May 15 18:23 messages
-rw-r–r-- 1 root root 102463 May 15 14:29 messages.0
-rw-r–r-- 1 root root 102476 May 15 02:57 messages.1
-rw-r–r-- 1 root root 102463 May 14 15:47 messages.2
-rw-r–r-- 1 root root 102470 May 14 04:15 messages.3
-rw-r–r-- 1 root root 102463 May 13 16:49 messages.4
-rw-r–r-- 1 root root 102470 May 13 05:17 messages.5
“messages” and “lastlog” are current, “messages.0” through “messages.5” are backups. After reboot, check in there. Most likely, some watchdog action was the reason.
restart its network stack
