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
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).
I originally posted this on the "running CumulusMX as a service but didn't receive any responses. Still dealing with the issue and just wondering if anyone has any ideas.
While rebuilding my rPi compute module 4 with Bullseye 64 bit I've encountered a problem on "reboot". I've encountered a problem that I can't find a solution to. I have CumulusMX running on a rPi 4 with Bullseye 64 bit set up exactly the same but runs without issue.
After reboot I check "sudo systemctl status cumulusmx" and MX starts up but at the end of the report:
● cumulusmx.service - CumulusMX service
Loaded: loaded (/etc/systemd/system/cumulusmx.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2022-03-10 17:28:30 CST; 42s ago
Docs: https://cumuluswiki.org/a/Main_Page
Process: 381 ExecStart=/usr/bin/mono-service -d:/home/pi/CumulusMX CumulusMX.exe -service (code=exited, status=0/SUCCESS)
Main PID: 382 (mono)
Tasks: 11 (limit: 8987)
CPU: 5.568s
CGroup: /system.slice/cumulusmx.service
└─382 /usr/bin/mono /usr/lib/mono/4.5/mono-service.exe -d:/home/pi/CumulusMX CumulusMX.exe -service
Mar 10 17:28:29 rPi-computemod-4 systemd[1]: Starting CumulusMX service...
Mar 10 17:28:30 rPi-computemod-4 systemd[1]: Started CumulusMX service.
Mar 10 17:28:36 rPi-computemod-4 mono[382]: CumulusMX.exe: Object reference not set to an instance of an object
When I ""sudo systemctl reboot cumulusmx" everything is fine.
retreat at augusta pines weather CumulusMX on Raspberry πrPi5 http://augusta-pines-weather.com / CumulusMX 4.1.2 build:4027 WeatherUnderground KTXSPRIN538
You have it running there
● cumulusmx.service - CumulusMX service
Loaded: loaded (/etc/systemd/system/cumulusmx.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2022-03-10 17:28:30 CST; 42s ago
that last error you see is an error from mono, so is it recording data? so, to see if it is, open up the current mxdiag file and see if it updates. And if there are any errors within the file, post it here and Mark or others can help out
jlmr731 wrote: ↑Sun 20 Mar 2022 11:13 pm
You have it running there
● cumulusmx.service - CumulusMX service
Loaded: loaded (/etc/systemd/system/cumulusmx.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2022-03-10 17:28:30 CST; 42s ago
that last error you see is an error from mono, so is it recording data? so, to see if it is, open up the current mxdiag file and see if it updates. And if there are any errors within the file, post it here and Mark or others can help out
jlmr, good news, saw another post that Mark handled about Cumulus stalls at startup, on version 3171. The discussion was similar to my issue in that it seemed to hang at the start with mono, Mark, Hans et. all added start up delay with ping. I added both and it cured my issue.
Thanks for the assistance.
Steve
retreat at augusta pines weather CumulusMX on Raspberry πrPi5 http://augusta-pines-weather.com / CumulusMX 4.1.2 build:4027 WeatherUnderground KTXSPRIN538
Good to hear startup delay works. Did see in your diag that the network is not fully up when MX starts you can see when it first checks for update github not found.
No, I've not been very lucky looking at the logs, there's usually so much there and I don't have an IT background looking at logs, although I'm getting better at it. The cause and effect relationships don't pop out.
Again, thanks for the help.
Steve
retreat at augusta pines weather CumulusMX on Raspberry πrPi5 http://augusta-pines-weather.com / CumulusMX 4.1.2 build:4027 WeatherUnderground KTXSPRIN538
f4phlyer wrote: ↑Sun 20 Mar 2022 9:02 pm
I originally posted this on the "running CumulusMX as a service but didn't receive any responses. Still dealing with the issue and just wondering if anyone has any ideas.
While rebuilding my rPi compute module 4 with Bullseye 64 bit I've encountered a problem on "reboot". I've encountered a problem that I can't find a solution to. I have CumulusMX running on a rPi 4 with Bullseye 64 bit set up exactly the same but runs without issue.
After reboot I check "sudo systemctl status cumulusmx" and MX starts up but at the end of the report:
● cumulusmx.service - CumulusMX service
Loaded: loaded (/etc/systemd/system/cumulusmx.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2022-03-10 17:28:30 CST; 42s ago
Docs: https://cumuluswiki.org/a/Main_Page
Process: 381 ExecStart=/usr/bin/mono-service -d:/home/pi/CumulusMX CumulusMX.exe -service (code=exited, status=0/SUCCESS)
Main PID: 382 (mono)
Tasks: 11 (limit: 8987)
CPU: 5.568s
CGroup: /system.slice/cumulusmx.service
└─382 /usr/bin/mono /usr/lib/mono/4.5/mono-service.exe -d:/home/pi/CumulusMX CumulusMX.exe -service
Mar 10 17:28:29 rPi-computemod-4 systemd[1]: Starting CumulusMX service...
Mar 10 17:28:30 rPi-computemod-4 systemd[1]: Started CumulusMX service.
Mar 10 17:28:36 rPi-computemod-4 mono[382]: CumulusMX.exe: Object reference not set to an instance of an object
When I ""sudo systemctl reboot cumulusmx" everything is fine.
You say 'When I ""sudo systemctl reboot cumulusmx" everything is fine'. Do you still have the Object reference error in the status call after you reboot it?
A lot of times when I see these one off errors it's typically a corrupted monthly log file. Not saying that's it, but in my experience (I've been running CMX now since 2016) that's almost always it.
In a lot of cases, the MXdiag log file will have entries like the following if that's the case.
2021-12-15 12:05:59.728 Error parsing log file record: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
2021-12-15 12:05:59.728 LoadRecent: Error at line 4178 of data/Dec21log.txt : Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
You say 'When I ""sudo systemctl reboot cumulusmx" everything is fine'. Do you still have the Object reference error in the status call after you reboot it?
A lot of times when I see these one off errors it's typically a corrupted monthly log file. Not saying that's it, but in my experience (I've been running CMX now since 2016) that's almost always it.
In a lot of cases, the MXdiag log file will have entries like the following if that's the case.
Thanks for the comment, armed with your’s and ‘jamir 731’s comments. I’ll do a little more digging to see to what extant the problem is/was. The issue arose as I was rebuilding a rPi compute module on a rPi CM4 i/O board with 64 bit Raspian. Jeff Geerling has suggested that 32 bit Debian will be loosing support in the new 64 bit world so I thought I’d get start the transition.
retreat at augusta pines weather CumulusMX on Raspberry πrPi5 http://augusta-pines-weather.com / CumulusMX 4.1.2 build:4027 WeatherUnderground KTXSPRIN538
I originally thought I had a problem with mono, it seems that 'mono' for Raspian is only 32 bit. I was transitioning to Raspian 64bit so was thinking that it was a mono problem.
More or less wrapping this up, looking a little deeper there may be something else but what stopped the startup of MX was it stopped when the ping request for the web site didn't respond prior to the minimum timeout. So setting the ping wait time to 10 solved it.
retreat at augusta pines weather CumulusMX on Raspberry πrPi5 http://augusta-pines-weather.com / CumulusMX 4.1.2 build:4027 WeatherUnderground KTXSPRIN538
No, I've not been very lucky looking at the logs, there's usually so much there and I don't have an IT background looking at logs, although I'm getting better at it. The cause and effect relationships don't pop out.