"Data stopped" - help please!

[Defenderdogs]

I am experience regular "Data Stopped" issues and am struggling to work out why this is happening. A sample of the latest log shows the following (starting from the first thing that looks 'odd') -

2024-11-12 09:45:33.169 ZeroConf Service: WLL service has been removed!
2024-11-12 09:45:33.180 ZeroConf Service: AirLink airlink-1000CE service has been removed!
2024-11-12 09:45:33.180 ZeroConf Service: AirLink airlink-1005A1 service has been removed!
2024-11-12 09:45:33.188 ZeroConf Service: AirLink airlink-1000CE service has been removed!
2024-11-12 09:45:33.189 ZeroConf Service: AirLink airlink-1005A1 service has been removed!
2024-11-12 09:45:38.600 WLL: Missed a WLL broadcast message. Percentage good packets 99.31% - (5,720)
2024-11-12 09:45:39.252 GetWllCurrent: Sending GET current conditions request 1 to WLL: http://192.168.1.10/v1/current_conditions ...
2024-11-12 09:45:40.264 GetWllCurrent: Sending GET current conditions request 2 to WLL: http://192.168.1.10/v1/current_conditions ...
2024-11-12 09:45:41.274 GetWllCurrent: Sending GET current conditions request 3 to WLL: http://192.168.1.10/v1/current_conditions ...
2024-11-12 09:45:41.278 GetWllCurrent: Error processing WLL response
2024-11-12 09:45:41.279 GetWllCurrent: Base exception - Network is unreachable
2024-11-12 09:45:41.279 ERROR: No current data received from the WLL, DataStopped triggered
2024-11-12 09:45:41.280 Alarm (Data Stopped): Triggered, value = True, threshold = 0, Message = No current data is being received from the WLL
2024-11-12 09:45:41.603 WLL: Missed a WLL broadcast message. Percentage good packets 99.17% - (6,720)
2024-11-12 09:45:43.787 ZeroConf Service: + 'weatherlinklive-7153e7' on eth0
2024-11-12 09:45:43.788 Host: weatherlinklive-7153e7 (192.168.1.10)
2024-11-12 09:45:43.788 ZeroConf Service: WLL found, reporting its IP address as: 192.168.1.10
2024-11-12 09:45:43.873 WLL Broadcast: {"did":"001D0A7153E7","ts":1731404742,"conditions":[{"lsid":473155,"data_structure_type":1,"txid":1,"wind_speed_last":13.00,"wind_dir_last":324,"rain_size":2,"rain_rate_last":0,"rain_15_min":0,"rain_60_min":0,"rain_24_hr":0,"rain_storm":0,"rain_storm_start_at":null,"rainfall_daily":0,"rainfall_monthly":1,"rainfall_year":1601,"wind_speed_hi_last_10_min":21.00,"wind_dir_at_hi_speed_last_10_min":336}]}

It looks like it is telling me that the WLL isn't sending data, but at the bottom seems to be picking up the broadcast data. The monthly file is being updated every 5 minutes as I would expect.

The only thing that has changed recently is that I moved the system from a RPi3 to a slightly more powerful Odroid C2 running Ubuntu 20.04.

Can anyone help me sort this out?

[freddie]

2024-11-12 09:45:41.279 GetWllCurrent: Base exception - Network is unreachable

Looks like the server that MX is running on is intermittently losing its network connection. There may be other evidence of this in your system log, or via journalctl.

[Defenderdogs]

You were right although I thought I had sorted that. Before I installed CMX I turned off all the power saving/sleep options in the UI and every time I checked after seeing the Data Stopped message, the network connection was active. It seems disabling the UI power saving options isn't enough, however, and I needed to disable a few more on the command line.

Looking more closely at the logs, it seems it was sleeping for a few seconds then waking up again. Am I correct that, if I uncheck the "Trigger DataStopped on Broadcast stop" option in the Station Settings, that CMX would 'recover' in the situation where the comms were down for just a few seconds?

[mcrossley]

Am I correct that, if I uncheck the "Trigger DataStopped on Broadcast stop" option in the Station Settings, that CMX would 'recover' in the situation where the comms were down for just a few seconds?

That setting will not make any difference to how Cumulus recovers.