Is this normal behaviour?

[Mapantz]

I've been doing a lot of work on cable management for my office space today. Several times, I have had to pull the plug on the AC to to the WLL, just for a few seconds whilst moving stuff.

Code: Select all

2023-12-16 21:00:41 - ERROR: No broadcast data received from the WLL for 30 seconds
2023-12-16 21:00:11 - ERROR: No broadcast data received from the WLL for 30 seconds
2023-12-16 20:59:41 - ERROR: No broadcast data received from the WLL for 30 seconds
2023-12-16 20:59:11 - ERROR: No broadcast data received from the WLL for 30 seconds

CMX never resyncs with the WLL properly after that. Several minutes in, it'll update maybe once every 30 seconds or so, but that's it. I have to restart CMX completely to get it working normally.

[PaulMy]

Not caused by pulling the plug, just normal behaviour...
Full log since just before previous day end.

Code: Select all

2023-12-16 16:20:15 - WOW update: A task was canceled.
2023-12-16 15:20:00 - WOW Response: ERROR - Response code = 429, body = The custom error module does not recognize this error.
2023-12-16 15:15:15 - WOW update: A task was canceled.
2023-12-16 14:35:46 - ERROR: No broadcast data received from the WLL for 30 seconds
2023-12-16 13:31:15 - ERROR: No broadcast data received from the WLL for 30 seconds
2023-12-16 13:11:15 - ERROR: No broadcast data received from the WLL for 30 seconds
2023-12-16 12:36:44 - ERROR: No broadcast data received from the WLL for 30 seconds
2023-12-16 12:35:01 - WOW Response: ERROR - Response code = 429, body = The custom error module does not recognize this error.
2023-12-16 12:31:14 - ERROR: No broadcast data received from the WLL for 30 seconds
2023-12-16 12:30:15 - WOW update: A task was canceled.
2023-12-16 12:16:14 - ERROR: No broadcast data received from the WLL for 30 seconds
2023-12-16 12:11:44 - ERROR: No broadcast data received from the WLL for 30 seconds
2023-12-16 10:55:00 - WOW Response: ERROR - Response code = 429, body = The custom error module does not recognize this error.
2023-12-16 10:50:15 - WOW update: A task was canceled.
2023-12-16 10:30:01 - WOW Response: ERROR - Response code = 429, body = The custom error module does not recognize this error.
2023-12-16 10:25:15 - WOW update: A task was canceled.
2023-12-16 10:06:12 - ERROR: No broadcast data received from the WLL for 30 seconds
2023-12-16 08:55:00 - WOW Response: ERROR - Response code = 429, body = The custom error module does not recognize this error.
2023-12-16 08:50:00 - WOW Response: ERROR - Response code = 429, body = The custom error module does not recognize this error.
2023-12-16 08:46:41 - ERROR: No broadcast data received from the WLL for 30 seconds
2023-12-16 08:45:01 - WOW Response: ERROR - Response code = 429, body = The custom error module does not recognize this error.
2023-12-16 08:40:15 - WOW update: A task was canceled.
2023-12-16 08:21:10 - ERROR: No broadcast data received from the WLL for 30 seconds
2023-12-16 06:50:00 - WOW Response: ERROR - Response code = 429, body = The custom error module does not recognize this error.
2023-12-16 06:45:00 - WOW Response: ERROR - Response code = 429, body = The custom error module does not recognize this error.
2023-12-16 06:40:12 - WOW Response: ERROR - Response code = 429, body = The custom error module does not recognize this error.
2023-12-16 06:15:01 - PHP[Int]: Error uploading to airlinkrealtime.txt - An error occurred while sending the request.
2023-12-16 05:11:07 - ERROR: No broadcast data received from the WLL for 30 seconds
2023-12-16 03:10:00 - WOW Response: ERROR - Response code = 429, body = The custom error module does not recognize this error.
2023-12-16 03:05:00 - WOW Response: ERROR - Response code = 429, body = The custom error module does not recognize this error.
2023-12-16 03:00:00 - WOW Response: ERROR - Response code = 429, body = The custom error module does not recognize this error.
2023-12-16 02:55:15 - WOW update: A task was canceled.
2023-12-16 02:51:35 - ERROR: No broadcast data received from the WLL for 30 seconds
2023-12-16 02:33:24 - Wunderground: ERROR - A task was canceled.
2023-12-16 02:05:01 - WOW Response: ERROR - Response code = 429, body = The custom error module does not recognize this error.
2023-12-16 02:00:01 - WOW Response: ERROR - Response code = 429, body = The custom error module does not recognize this error.
2023-12-16 01:55:15 - WOW update: A task was canceled.
2023-12-16 01:45:01 - WOW Response: ERROR - Response code = 429, body = The custom error module does not recognize this error.
2023-12-16 01:40:15 - WOW update: A task was canceled.
2023-12-16 01:11:34 - ERROR: No broadcast data received from the WLL for 30 seconds
2023-12-16 01:02:04 - ERROR: No broadcast data received from the WLL for 30 seconds
2023-12-16 00:40:00 - WOW Response: ERROR - Response code = 429, body = The custom error module does not recognize this error.
2023-12-16 00:35:00 - WOW Response: ERROR - Response code = 429, body = The custom error module does not recognize this error.
2023-12-16 00:30:15 - WOW update: A task was canceled.
2023-12-16 00:02:03 - ERROR: No broadcast data received from the WLL for 30 seconds
2023-12-16 00:00:17 - PHP[Int]: Error uploading to alltempsumdata.json - A task was canceled.
2023-12-16 00:00:12 - PHP[Int]: Error uploading to alldailyhumdata.json - A task was canceled.
2023-12-16 00:00:12 - PHP[Int]: Error uploading to alldailytempdata.json - A task was canceled.
2023-12-16 00:00:07 - PHP[Int]: Error uploading to dayfile.txt - A task was canceled.
2023-12-15 23:53:33 - ERROR: No broadcast data received from the WLL for 30 seconds

[mcrossley]

CMX never resyncs with the WLL properly after that. Several minutes in, it'll update maybe once every 30 seconds or so, but that's it. I have to restart CMX completely to get it working normally.

CMX doesn't really do anything active++ with the WLL broadcast data. It just sits there listening on the network for the WLL to send them.

++ Not quite true, the WLL only sends the broadcasts when something requests them. Every time you get the error message about broadcasts not being received, it sends a message to the WLL to restart broadcasting.