Cumulus Support

Hello everyone,

Since I started it, I have seen 2 sudden stops of the cumulus which was not responding anymore.
However, the last one took place during my absence and I find myself on my site with a huge hole in the data.
Wouldn't it be possible to integrate a script on the raspberry (yes I'm on raspberry pi lite, I'm using the image provided in the wiki) that regularly checks if Cumulus is active (for example by looking at the date of edition of a file it's supposed to modify every X seconds) and if it's not the case (for example this file has been edited more than 5 minutes ago), it runs :
sudo systemctl stop cumulusmx (to make sure you stop it)
and immediately :
sudo systemctl start cumulusmx.

In this way, sudden stops would be prevented and the risk of losing data would be greatly reduced.

Thank you!

Translated with www.DeepL.com/Translator (free version)

Sudden stops are unusual - please zip up the log files from your MXdiags folder and attach to a reply to this topic.

If you run MX as a service then you can configure the service to restart on failure. But it would be good to see your log files to track down what is causing the sudden stop.

Thanks for the reply!
It was mainly during the times I was setting it up and doing a major FTP transfer or something but I'll check. Since I haven't touched it anymore it's holding.
However I am interested to know how to restart cumulus automatically in case of failure (I use it as a service indeed) ?
Thanks for your help.

Benji60 wrote: ↑Sat 16 Oct 2021 12:58 pmHowever I am interested to know how to restart cumulus automatically in case of failure (I use it as a service indeed) ?

Add the following to the [Service] section of your cumulusmx.service unit file:
Don't forget to run the following after making a change to the unit file:

Hello,

I have just one remark. I had to reboot my raspberry yesterday and I noticed that the connection with my GW100 is not very good at startup. All the data except the pressure remain at 0.
I have to do the commands: "sudo systemctl stop cumulusmx" then "sudo systemctl start cumulusmx" to make it work again.
After several boot I notice that it is systematically the case.

It is rather problematic because in case of absence or power cut the reboot will be out of order.

I have the last update of cumulus and my device is also up to date.

Thank you !

I suggest you try using some of the Start-Up options in the Program Settings as Mark put this in to combat this type of problem.

You can delay a number seconds, ping the host to check it is up, base it on system up-time etc. I am sure one of these will solve the problem.

freddie wrote: ↑Sun 17 Oct 2021 10:39 am

Benji60 wrote: ↑Sat 16 Oct 2021 12:58 pmHowever I am interested to know how to restart cumulus automatically in case of failure (I use it as a service indeed) ?

Add the following to the [Service] section of your cumulusmx.service unit file:

Code: Select all

Restart=always
RestartSec=10

Don't forget to run the following after making a change to the unit file:

Code: Select all

sudo systemctl daemon-reload

I didn't know you could do this!
I presume this will not restart CMX after a manual shutdown via sudo systemctl stop cumulusmx

Just to confirm my cumulus.service file should look this this?


[Unit]
Description=CumulusMX service
Documentation=https://cumuluswiki.org/a/Main_Page
After=network-online.target

[Service]
User=root
Group=root
ExecStart=/usr/bin/mono-service -d:/home/pi/CumulusMX CumulusMX.exe -service
Type=forking
ExecStopPost=/bin/rm /tmp/CumulusMX.exe.lock
Restart=always
RestartSec=10

[Install]
WantedBy=multi-user.target

Thank you for the answer,
It seems that a 10 second delay after startup works.