Version 3.60-80 has been running stably in my environment for a few days, even with Node-RED and GUI v1 enabled on the Ekrano itself. However, today I tried enabling GUI v2 directly on the Ekrano, and it crashed after about two hours. This reboot issue has been present across many previous versions. My next step is to update to -83…
Hi,
Most likely this is due to CPU overload - check your flows, or check if it happens without running Node-RED / having that disabled.
For further troubleshooting of that, please use another category - not the beta category. This is 99% sure not a bug.
Thanks!
Sure, that’s what I thought too. But the system load is OK as long as I don’t activate the GUI V2. I only have reboots when Gui v2 is enabled on the Ekrano.
Here is a top with GUI v1
Mem: 680232K used, 348848K free, 13284K shrd, 30492K buff, 202140K cached
CPU: 32% usr 4% sys 0% nic 60% idle 0% io 1% irq 0% sirq
Load average: 2.48 2.02 2.56 5/317 13408
PID PPID USER STAT VSZ %VSZ %CPU COMMAND
813 804 root R 288m 29% 7% /opt/victronenergy/gui/gui -neatvnc 127.0.0.1
1459 823 nodered S 219m 22% 4% node-red
556 555 messageb R 3960 0% 3% dbus-daemon --system --nofork
875 854 root R 30980 3% 3% {dbus_systemcalc} /usr/bin/python3 -u /opt/victronenergy/dbus-systemcalc-py/dbus_systemcalc.py
801 793 root R 44480 4% 3% {vrmlogger.py} /usr/bin/python3 -u /opt/victronenergy/vrmlogger/vrmlogger.py
1486 1474 root S 47916 5% 2% /usr/bin/flashmq
1742 1740 root S 35912 3% 2% python /data/dbus-solar-haus/dbus-solar-haus.py
1535 1531 root S 22640 2% 1% /opt/victronenergy/dbus-modbustcp/dbus-modbustcp
The problem exists since the Gui v2 was introduced on the Ekrano or Cerbo it self. I think it is a bug in the module that represents the GUI.
I have already tested so much and also a complete new installation. Also with and without Node-Red. After an indefinite time the Ekrano restarts when the GUi v2 is enabled on the device. The reboots are the reason why I started testing the beta in the first place. Yes I also have some installations with Ekrano and GuiV2 which are stable also these use Node-Red with similar flows.
Isn’t it just gui-v2 having a higher load?
Though 60% idle is not bad. You could check the reason for reboot by checking /data/logs/messages, and messages.0 etc
Here is the log. messeges.0
Yes the reboot is because of high load. I switched to the GUI v2 around 12:00.
May 29 02:25:53 ekrano cron.info CROND[8237]: (root) CMDOUT (Retrieving latest version… (from https://updates.victronenergy.com/feeds/venus/candidate/images/ekrano/venus-swu-large-ekrano.swu))
May 29 02:25:53 ekrano cron.info CROND[8237]: (root) CMDOUT (installed: 20250524142208 v3.60~80)
May 29 02:25:53 ekrano cron.info CROND[8237]: (root) CMDOUT (available: 20250528080456 v3.60~83)
May 29 02:25:53 ekrano cron.info CROND[8237]: (root) CMDEND (/opt/victronenergy/swupdate-scripts/check-updates.sh -auto -delay)
May 29 13:42:12 ekrano daemon.err watchdog[434]: loadavg 11 8 7 is higher than the given threshold 0 10 6!
May 29 13:42:13 ekrano daemon.err watchdog[434]: repair binary /usr/sbin/store_watchdog_error.sh returned 253 = ‘load average too high’
May 29 13:42:13 ekrano daemon.alert watchdog[434]: shutting down the system because of error 253 = ‘load average too high’
May 29 13:42:13 ekrano daemon.err watchdog[26126]: /usr/sbin/sendmail does not exist or is not executable (errno = 2)
May 29 13:42:14 ekrano syslog.info syslogd exiting
May 29 13:44:26 ekrano syslog.info syslogd started: BusyBox v1.36.1
TOP with gui-V2 the load is significantly higher and growing :
Mem: 687932K used, 341148K free, 18428K shrd, 33084K buff, 229200K cached
CPU: 52% usr 10% sys 0% nic 32% idle 0% io 2% irq 1% sirq
Load average: 10.30 7.07 4.43 20/320 18252
PID PPID USER STAT VSZ %VSZ %CPU COMMAND
17208 804 root R 237m 24% 28% /opt/victronenergy/gui-v2/venus-gui-v2
1459 823 nodered S 219m 22% 5% node-red
556 555 messageb S 3964 0% 4% dbus-daemon --system --nofork
875 854 root R 30980 3% 4% {dbus_systemcalc} /usr/bin/python3 -u /opt/victronenergy/dbus-systemcalc-py/dbus_systemcalc.py
801 793 root S 44480 4% 3% {vrmlogger.py} /usr/bin/python3 -u /opt/victronenergy/vrmlogger/vrmlogger.py
1486 1474 root S 48300 5% 2% /usr/bin/flashmq
888 877 root S 93336 9% 2% {dbus-modbus-cli} /usr/bin/python3 -u /opt/victronenergy/dbus-modbus-client/dbus-modbus-client.py
when I switch back, the load decreases again and the load drops. I have no problem with using V1 because I usually look at it remotely and V2 works, but I thought it should work reliably?