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

Problems Starting As A service

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

User avatar
The Dalek Hunter
Posts: 342
Joined: Wed 05 Aug 2020 11:51 am
Weather Station: Vantage Pro 2, Ecowitt GW2000
Operating System: macOS Sonoma on a Mac Mini M2
Contact:

Re: Problems Starting As A service

Post by The Dalek Hunter »

With debugging enabled the only files that turn up in in the MXdiags folder are attached
You do not have the required permissions to view the files attached to this post.
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: Problems Starting As A service

Post by mcrossley »

It doesn't look like there is any network connectivity when CMX starting up...

Code: Select all

Failed to get the latest build version from Github: No such host is known
Shows it cannot resolve github in DNS.

Then the crash happens when it tries to connect to your WLL IP address weatherlink.com.

Did you reboot the server and let CMX autostart for this log file?

I see you have no start-up delay configured.

Code: Select all

No start-up delay - disabled
You could try adding 30 seconds or a minute delay in there to give the host time to get things sorted out.
User avatar
The Dalek Hunter
Posts: 342
Joined: Wed 05 Aug 2020 11:51 am
Weather Station: Vantage Pro 2, Ecowitt GW2000
Operating System: macOS Sonoma on a Mac Mini M2
Contact:

Re: Problems Starting As A service

Post by The Dalek Hunter »

I added the debug option in the ini file and then rebooted.

I have been running it with a 30 second startup delay and with this it is fine.

I removed the startup delay for this test - I have now reinstated it and all is well
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: Problems Starting As A service

Post by mcrossley »

Yeah - sorry, I'd forgotten this history on this thread - I'll add a catch for the crash connecting to weatherlink.com.
User avatar
The Dalek Hunter
Posts: 342
Joined: Wed 05 Aug 2020 11:51 am
Weather Station: Vantage Pro 2, Ecowitt GW2000
Operating System: macOS Sonoma on a Mac Mini M2
Contact:

Re: Problems Starting As A service

Post by The Dalek Hunter »

Many thanks
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: Problems Starting As A service

Post by mcrossley »

Looks like I already did it! Also looking more closely it was the code that connected to a service that provides status information ABOUT weatherlink.com that was causing the problem.
Cortmalaw
Posts: 92
Joined: Sat 26 Dec 2020 2:21 pm
Weather Station: Davis
Operating System: Raspbian
Location: Near Glasgow, Scotland, UK

Re: Problems Starting As A service

Post by Cortmalaw »

The Dalek Hunter wrote: Mon 26 Apr 2021 11:05 am As the start by Cron has a delay of 30 seconds I tried that and it now starts perfectly.
I will leave it at that without any further meddling :)
I can confirm that the 30 sec delay when started as a cron job was intended to allow time for the network to come up and stabilise. Time was found empirically.
Post Reply