Nope, not a beta version…
For example, SignalK, I have an app that forwards AIS data, and every week to month, it will just stop acknowledging that data coming in. The AIS transceiver still broadcast, and the AIS data shows on the networked chart plotters, so its not an AIS or network issue, it is solely inside the Cerbo…
I dont know if it is the cause or related, but this is on a boat with a lot of NMEA traffic…
SignalK can be hungry,
If you ssh in to the device and run top it should give you a good idea what is eating up cpu time, but your issue doesn’t sound like cpu - the watchdog would force a reboot.
Maybe a memory leak somewhere.
Another issue that pops up is filling up data partitions with logging.
Some careful diagnosis should be able to point towards the cause.
I had logging on, and had that issue, but since turned that off.
How can you check memory leaks?
Top will show what is consumed, you can use ps commands as well.
You would be looking for the amount of total free memory declining and processes that are consuming large amounts.
Since your issue is quite slow, you should be able to find a trend.
There are ways to chart some of this via nodered flows as well.
A good metric for cpu constraints is the gateway dbus round trip time advanced widget in VRM. Big spikes indicate resource issues.
This is from mine, which is normal, the spike was a result of heavy usage after an OS update. This is tracked historically so you can add the widget and rewind to days you had issues.
If you prefer I can split out this thread from the main topic.
Moved to a new topic in Mods, change the title as appropriate.
Can definitely see high service times in the March chart.
