I left MX running on the RPi over night, this morning when I try and fire up the admin web page there is no live data.
All the HTML and related files download OK, but the websockets session times out after 4 minutes with no data retrieved.
Nothing interesting on the program console, just the usual connects/disconnects... (Dah! I closed it trying to copy the contents - I'll screen grab next time!).
Diags attached, two items of note. At 22:44 last night the wrong cable got pulled out of the router, hence a block of network errors.
Then at 04:46, there was some sort of file share contention on upload. I can't see anything else of note.
On restarting everything is running clean, no errors.
So probably nothing you can do, but just a point of reference.
Welcome to the Cumulus Support forum.
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Cumulus MX V4 beta test release 4.0.0 (build 4018) - 28 March 2024
Legacy Cumulus 1 release v1.9.4 (build 1099) - 28 November 2014 (a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Cumulus MX V4 beta test release 4.0.0 (build 4018) - 28 March 2024
Legacy Cumulus 1 release v1.9.4 (build 1099) - 28 November 2014 (a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
MX Dashboard failed
Moderator: mcrossley
- mcrossley
- Posts: 12694
- Joined: Thu 07 Jan 2010 9:44 pm
- Weather Station: Davis VP2/WLL
- Operating System: Bullseye Lite rPi
- Location: Wilmslow, Cheshire, UK
- Contact:
MX Dashboard failed
You do not have the required permissions to view the files attached to this post.
- steve
- Cumulus Author
- Posts: 26702
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: MX Dashboard failed
Could be that the network problem killed the websocket server. I'll see if there are any useful looking settings.
Steve