3.50~18 vrmlogger restarting

Hi,

Since ~4:30 (CEST) this morning vrmlogger is stopped working for me.
I got a ‘no data’ alarm in VRM and when logging into VRM I see realtime data, but no historical graphs.
Since realtime is working, I can conclude that it is not a network related issue on the cerbo side.

Digging deeper into this, I noticed this is probably due to the following error in vrmlogger

@4000000066dadd5b241f6214 *** starting vrmlogger ***
@4000000066dadd601cc23884 MainThread-vrmlogger: /opt/victronenergy/vrmlogger/vrmlogger.py v2.337 is starting up
@4000000066dadd601ccf6b6c MainThread-vrmlogger: Loglevel set to INFO
@4000000066dadd601dffe8a4 MainThread-vedbus: registered ourselves on D-Bus as com.victronenergy.logger
@4000000066dadd6025b7f7bc MainThread-dbusmonitor: ===== Search on dbus for services that we will monitor starting... =====
@4000000066dadd6025f72b6c MainThread-dbusmonitor: Found: com.victronenergy.temperature.adc_builtin0_5, scanning and storing items
@4000000066dadd60263307a4 MainThread-dbusmonitor:        com.victronenergy.temperature.adc_builtin0_5 has device instance 23
@4000000066dadd6027f8b05c MainThread-dbusmonitor: Found: com.victronenergy.temperature.adc_builtin0_6, scanning and storing items
@4000000066dadd60283553cc MainThread-dbusmonitor:        com.victronenergy.temperature.adc_builtin0_6 has device instance 22
@4000000066dadd6029441c1c MainThread-dbusmonitor: Found: com.victronenergy.temperature.adc_builtin0_7, scanning and storing items
@4000000066dadd60297ef684 MainThread-dbusmonitor:        com.victronenergy.temperature.adc_builtin0_7 has device instance 21
@4000000066dadd602a736c8c MainThread-dbusmonitor: Found: com.victronenergy.hub4, scanning and storing items
@4000000066dadd602abcf4c4 MainThread-dbusmonitor:        com.victronenergy.hub4 has device instance 0
@4000000066dadd602b4ce46c MainThread-dbusmonitor: Found: com.victronenergy.settings, scanning and storing items
@4000000066dadd602b82b5c4 MainThread-dbusmonitor:        com.victronenergy.settings has device instance 0
@4000000066dadd60339d2474 MainThread-dbusmonitor: Found: com.victronenergy.battery.socketcan_can1, scanning and storing items
@4000000066dadd6033dae124 MainThread-dbusmonitor:        com.victronenergy.battery.socketcan_can1 has device instance 512
@4000000066dadd61123e111c MainThread-dbusmonitor: Found: com.victronenergy.acload.cg_BX14300190015, scanning and storing items
@4000000066dadd6112a264b4 MainThread-dbusmonitor:        com.victronenergy.acload.cg_BX14300190015 has device instance 42
@4000000066dadd6113c6d7e4 MainThread-dbusmonitor: Found: com.victronenergy.pvinverter.cg_BX1560089002C, scanning and storing items
@4000000066dadd6114359f44 MainThread-dbusmonitor:        com.victronenergy.pvinverter.cg_BX1560089002C has device instance 41
@4000000066dadd61169768bc MainThread-dbusmonitor: Found: com.victronenergy.system, scanning and storing items
@4000000066dadd611b625e4c MainThread-dbusmonitor:        com.victronenergy.system has device instance 0
@4000000066dadd61204089d4 MainThread-dbusmonitor: Found: com.victronenergy.vebus.ttyS4, scanning and storing items
@4000000066dadd61207ceadc MainThread-dbusmonitor:        com.victronenergy.vebus.ttyS4 has device instance 276
@4000000066dadd620c8fc454 MainThread-dbusmonitor: Found: com.victronenergy.grid.cg_BX16400200015, scanning and storing items
@4000000066dadd620ce48b74 MainThread-dbusmonitor:        com.victronenergy.grid.cg_BX16400200015 has device instance 40
@4000000066dadd620fdf29ec MainThread-dbusmonitor: Found: com.victronenergy.battery.socketcan_can0_vi0_uc358680, scanning and storing items
@4000000066dadd62101f385c MainThread-dbusmonitor:        com.victronenergy.battery.socketcan_can0_vi0_uc358680 has device instance 0
@4000000066dadd62264376ac MainThread-dbusmonitor: ===== Search on dbus for services that we will monitor finished =====
@4000000066dadd622d065824 MainThread-kwhdeltas: battery service not used #4
@4000000066dadd622d3693cc MainThread-kwhdeltas: battery service not used #4
@4000000066dadd622e59de1c MainThread-kwhdeltas: battery service not used #4
@4000000066dadd622e813854 MainThread-vrmlogger: Starting to log, vrmportal = 2, url = https://ccgxlogging.victronenergy.com/log/log.php
@4000000066dadd631f75852c MainThread-http_endpoint: Internal backlog buffer initialised. Count = 0
@4000000066dadd631f8991fc MainThread-http_endpoint: Found '/run/media/mmcblk0p1' as remembered external path
@4000000066dadd631fa1d8d4 MainThread-http_endpoint: Checking '/run/media/mmcblk0p1' for suitability for external storage
@4000000066dadd631ff5ec44 MainThread-http_endpoint: Found /run/media/mmcblk0p1 as external storage dir
@4000000066dadd63204ed214 MainThread-http_endpoint: Extra SQLite DB made at /run/media/mmcblk0p1/vrmlogger-backlog.sqlite3
@4000000066dadd632075e214 MainThread-http_endpoint: Made /run/media/mmcblk0p1/vrmlogger-backlog.sqlite3 the active buffer
@4000000066dadd63216d079c MainThread-http_endpoint: Starting sender thread. This will send data to the remote log server, of which the first success will be reported.
@4000000066dadd6321bd4a7c MainThread-http_endpoint: Started sender thread
@4000000066dadd632209d824 MainThread-http_endpoint: HttpEndpoint initialised, http worker thread running
@4000000066dadd6327de8524 Traceback (most recent call last):
@4000000066dadd6327e0f624   File "/opt/victronenergy/vrmlogger/vrmlogger.py", line 642, in <module>
@4000000066dadd63281c9bac     main()
@4000000066dadd63281ed214   File "/opt/victronenergy/vrmlogger/vrmlogger.py", line 621, in main
@4000000066dadd632848b4bc     start_logging(state)
@4000000066dadd63284a75f4   File "/opt/victronenergy/vrmlogger/vrmlogger.py", line 462, in start_logging
@4000000066dadd632871c474     send_data(state)
@4000000066dadd632871dbe4   File "/opt/victronenergy/vrmlogger/vrmlogger.py", line 320, in send_data
@4000000066dadd63288eba84     data.update(kwhdeltas.getdeltas(refreshbaseline=False))
@4000000066dadd6328905894   File "/opt/victronenergy/vrmlogger/kwhdeltas.py", line 516, in getdeltas
@4000000066dadd6328b94524     code = self._rawdeltas.get(serviceclass, {}).get(path)
@4000000066dadd6328bbbdf4 AttributeError: 'set' object has no attribute 'get'
@4000000066dadd6403114164 *** starting vrmlogger ***

So vrmlogger is constantly restarting, without reporting any data to the vrm website.
I’ve tried the basic troubleshooting of restarting the cerbo.

Installation: 464460
Setup:
MP2 (3x)
Cerbo (v3.50~18)
EM24 (Grid meter)
EM24 (PV Meter)
EM24 (Generic load meter, no function)
(I figured this might be importend information, since the error is about kwhdelta’s)

Im able to provide direct SSH access to the cerbo for diagnostics if necessary.

Notice realtime is on and realtime data is also acurate.
But all the graphs show the last datapoint of ~4:30 and the last realtime datapoint but is missing all the data in between. Also the realtime data isn’t saved, so when refreshing the graph is updated to the last known realtime value.

If you ssh to the device, are any of the partitions full?

root@cerbo:~# df -h
Filesystem                Size      Used Available Use% Mounted on
/dev/root                 1.1G      1.0G     59.0M  95% /
devtmpfs                454.5M      4.0K    454.5M   0% /dev
tmpfs                   503.0M    928.0K    502.1M   0% /run
tmpfs                   503.0M    252.0K    502.7M   0% /var/volatile
/dev/mmcblk1p5            4.6G     29.9M      4.3G   1% /data
/dev/mmcblk0p1            7.3G    387.1M      6.9G   5% /run/media/mmcblk0p1
tmpfs                   503.0M    928.0K    502.1M   0% /service

Doesn’t look like

I cant reply anymore because the thread is closed.
The bug is solved, dank je Matthijs

Hey @hp197 this was a bug, fixed per v3.50~20.

Thank you reporting!