Today over the night Cerbo lost can connection to all devices. I loaded logs /var/log/dbus-systemcalc-py/current and found the following
2025-11-03 22:47:50.208336500 INFO:dbusmonitor:com.victronenergy.multi.socketcan_can0_vi0_uc269838 disappeared from the dbus. Removing it from our lists
2025-11-03 22:47:50.485653500 INFO:dbusmonitor:com.victronenergy.multi.socketcan_can0_vi1_uc260959 disappeared from the dbus. Removing it from our lists
2025-11-03 22:47:50.565887500 INFO:dbusmonitor:com.victronenergy.multi.socketcan_can0_vi2_uc259646 disappeared from the dbus. Removing it from our lists
2025-11-03 22:47:50.646755500 INFO:dbusmonitor:com.victronenergy.grid.socketcan_can0_vi0_uc440792 disappeared from the dbus. Removing it from our lists
2025-11-03 22:47:50.749803500 INFO:dbusmonitor:com.victronenergy.acsystem.socketcan_can0_sys0 disappeared from the dbus. Removing it from our lists
2025-11-03 22:50:41.632511500 INFO:dbusmonitor:com.victronenergy.vecan.can0 disappeared from the dbus. Removing it from our lists
2025-11-03 22:50:41.927738500 INFO:dbusmonitor: com.victronenergy.vecan.can0 has device instance 0
Time is UTC.
In system there are 3xMultiRS single tracker version, MPPT 150 and Pytes stack with 8 batteries on BMS can (fw version 1.5.40.C8)
Cerbo restart fixed the problem, but the behavior is strange. Any ideas? I can give any other logs from this list
root@einstein:/var/log# ls
boot dbus-modbus-client flashmq messages.3 simple-upnpd venus-button-handler
boot~ dbus-modbustcp gui messages.4 socketcand venus-html5-app
can-bus-bms.can0 dbus-mqtt hiawatha messages.5 ssh-tunnel venus-html5-logger
can-bus-bms.can1 dbus-mqtt-integrations hostapd mk2_dbus.ttyS4 sshd venus-platform
crash-logger dbus-parallel-bms hub4control mosquitto start-gui vesmart-server
dbus-acsystem dbus-qwacs lastlog mqtt-rpc swupdate vrmlogger
dbus-adc dbus-shelly localsettings netmon vecan-dbus.can0 watchdog_processlist.txt
dbus-ble-sensors dbus-systemcalc-py messages nginx vedirect.ttyS5 websockify-c
dbus-digitalinputs dbus-vebus-to-pvinverter messages.0 node-red-venus vedirect.ttyS6 wtmp
dbus-fronius dmesg messages.1 serial-starter vedirect.ttyS7
dbus-generator-starter dmesg.old messages.2 service-advertiser venus-access
To add a bit: whole system went to off state of course, never tries to re-scan can bus
Also adding can port network stats
