Welcome to the Cumulus Support forum.

Latest Cumulus MX V4 release 4.4.2 (build 4085) - 12 March 2025

Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024

Legacy Cumulus 1 release 1.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

If you are posting a new Topic about an error or if you need help PLEASE read this first viewtopic.php?p=164080#p164080

Crash of build 3145

From build 3044 the development baton passed to Mark Crossley. Mark has been responsible for all the Builds since. He has made the code available on GitHub. It is Mark's hope that others will join in this development, but at the very least he welcomes your ideas for future developments (see Cumulus MX Development suggestions).

Moderator: mcrossley

Post Reply
User avatar
HansR
Posts: 6926
Joined: Sat 20 Oct 2012 6:53 am
Weather Station: GW1100 (WS80/WH40)
Operating System: Raspberry OS/Bookworm
Location: Wagenborgen (NL)
Contact:

Crash of build 3145

Post by HansR »

When running b3145 after a backup this morning and setting it up for remote extra sensors the system crashed. Noteworthy is that it did not crash completely, some threads remained. A restart was not quick but it took minutes, apparently waiting for a timeout.

When restarted the problem did not reappear so can't reproduce the error.

Logs attached.
You do not have the required permissions to view the files attached to this post.
Hans

https://meteo-wagenborgen.nl
CMX build 4070+ ● RPi 4B ● Linux 6.6.62+rpt-rpi-v8 aarch64 (bookworm) ● dotnet 8.0.1
BlueSky: https://bsky.app/profile/wagenborgenwx.bsky.social
Phil23
Posts: 888
Joined: Sat 16 Jul 2016 11:59 pm
Weather Station: Davis VP2+ & GW1000 (Standalone)
Operating System: Win10 Pro / rPi Buster
Location: Australia

Re: Crash of build 3145

Post by Phil23 »

Also saw something slightly strange on a restart after upgrading.

Will need to check all logs, but pretty sure it was one of the Pi's as my PC install's logs look fine.
:Now: :Today/Yesterday:

Image

Main Station Davis VP2+ Running Via Win10 Pro.
Secondary Stations, Ecowitt HP2551/GW1000 Via rPi 3 & 4 Running Buster GUI.
:Local Inverell Ecowitt Station: :Remote Ashford Ecowitt Station:
User avatar
mcrossley
Posts: 14388
Joined: Thu 07 Jan 2010 9:44 pm
Weather Station: Davis VP2/WLL
Operating System: Bullseye Lite rPi
Location: Wilmslow, Cheshire, UK
Contact:

Re: Crash of build 3145

Post by mcrossley »

There is a bit of a muddle in the standalone airlink code - it tries to use the WLL API key at one point. Fixed for next release.

Meantime, if you copy the standalone airlink API key, secret, station-id into the corresponding WLL values in Cumulus.ini to should avoid the crash.
User avatar
HansR
Posts: 6926
Joined: Sat 20 Oct 2012 6:53 am
Weather Station: GW1100 (WS80/WH40)
Operating System: Raspberry OS/Bookworm
Location: Wagenborgen (NL)
Contact:

Re: Crash of build 3145

Post by HansR »

mcrossley wrote: Fri 03 Sep 2021 10:35 am Meantime, if you copy the standalone airlink API key, secret, station-id into the corresponding WLL values in Cumulus.ini to should avoid the crash.
I have none of those, I use my own fake airlink so I just have an IP address.
And I just bought a AQM III which does exactly the same thing (fake an airlink by just the IP). Curious how that is going to work.

But we'll see if it re-occurs sometime at the same point with the next release.
So far all fixes have improved CMX so I have good confidence :D
Hans

https://meteo-wagenborgen.nl
CMX build 4070+ ● RPi 4B ● Linux 6.6.62+rpt-rpi-v8 aarch64 (bookworm) ● dotnet 8.0.1
BlueSky: https://bsky.app/profile/wagenborgenwx.bsky.social
User avatar
mcrossley
Posts: 14388
Joined: Thu 07 Jan 2010 9:44 pm
Weather Station: Davis VP2/WLL
Operating System: Bullseye Lite rPi
Location: Wilmslow, Cheshire, UK
Contact:

Re: Crash of build 3145

Post by mcrossley »

The code was checking for blank/null values, then using some other variables! :groan:

So yes, if you do not have any API values it may crash until I can get a patch released. I'll have to add that config to my testing, currently I was testing standalone and added to a WLL, but both with API keys.
Post Reply