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).
● cumulusmx.service - CumulusMX service
Loaded: loaded (/etc/systemd/system/cumulusmx.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2021-03-30 12:20:03 BST; 21min ago
Docs: https://cumuluswiki.org/a/Main_Page
Process: 22226 ExecStart=/usr/bin/mono-service -d:/opt/CumulusMX CumulusMX.exe -service (code=exited, status=0/SUCCESS)
Process: 13202 ExecStopPost=/bin/rm /tmp/CumulusMX.exe.lock (code=exited, status=0/SUCCESS)
Main PID: 22227 (code=exited, status=1/FAILURE)
Mar 30 12:20:03 cumulusmx systemd[1]: cumulusmx.service: Main process exited, code=exited, status=1/FAILURE
Mar 30 12:20:03 cumulusmx systemd[1]: cumulusmx.service: Failed with result 'exit-code'.
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
I've restarted the service and it's all running again but I wonder if there's anything I should look at for this or is it just 'one of those things'?
You could attach the latest log file from MXdiags to a reply to this topic. Also, look in /var/log/syslog for any entries around the time of the crash.
Mar 30 12:20:03 cumulusmx systemd[1]: cumulusmx.service: Main process exited, code=exited, status=1/FAILURE
Mar 30 12:20:03 cumulusmx systemd[1]: cumulusmx.service: Failed with result 'exit-code'.
Feek wrote: ↑Tue 30 Mar 2021 1:11 pmExcuse my ignorance, but how do I run MXdiags?
You don't. There is a directory/folder in your MX install that is called MXdiags. In this folder can be found the application's log files. Zip up the one that covers the period of your crash and attach it to a reply to this topic.
Got it, and I can see where the exception occurred - I'll get that fixed. The root cause was the GW1000 not responding to a command - read sensor ids new.
Though looking at the full log that appears to happen semi-regularly, along with read live data commands failing.
Anyway, looks fine apart from that, I get the code fixed to handle rouge responses better.
mcrossley wrote: ↑Tue 30 Mar 2021 2:58 pm
Got it, and I can see where the exception occurred - I'll get that fixed. The root cause was the GW1000 not responding to a command - read sensor ids new.
Though looking at the full log that appears to happen semi-regularly, along with read live data commands failing.
Anyway, looks fine apart from that, I get the code fixed to handle rouge responses better.
Just had another crash, here's the service status output and the latest MXdiags log is attached.
I can fix the crash, but I could really do with a log file capturing with debug and data logging enabled so I can see exactly why the response is invalid.
mcrossley wrote: ↑Thu 08 Apr 2021 8:41 pm
I can fix the crash, but I could really do with a log file capturing with debug and data logging enabled so I can see exactly why the response is invalid.
Just switch on debug and data logging from Program Settings | Program General Options.
Then if it crashes again before I get the next release out, please post the the MXdiags log file - it may get fairly large, I'll only really be interested in the last few pages before the crash.
mcrossley wrote: ↑Fri 09 Apr 2021 2:11 pm
Just switch on debug and data logging from Program Settings | Program General Options.
Then if it crashes again before I get the next release out, please post the the MXdiags log file - it may get fairly large, I'll only really be interested in the last few pages before the crash.