Cumulus MX go in auto-off at 01:10

[rchi]

Greetings to everyone, I just installed the new version of cumulus mx, but it happens to me that at night, at 01.10, the program closing procedure starts, while the Raspberry remains turned on... Why?

[freddie]

Could you please zip up the MXdiags log file that captures the shutdown and attach it to a reply to this topic? You could perhaps attach /var/log/syslog too.

[rchi]

Thanks for the reply, here is the part of the log that describes what happened.
I specify that it refers to the new station that I am preparing on a new Raspberry 4. Thanks

[rchi]

Ah...for the other file I don't have a syslog file or var/log folders... why?

[freddie]

You should have a /var/log/ directory - it's standard on Linux and Pi's.

[sutne]

It is not on Bookworm anymore.
It uses journalctl, but I haven’t really figured it out.

Edit: maybe this command will show something:

Code: Select all

journalctl | grep cumulusmx

[rchi]

Hi Freddie and thanks again for the help you are providing me because I really can't get out of it. To clarify things for you: I'm working on a new system installation with Cumulus MX, I'm setting up Cumulus and things seem to be going well. At the moment the only problem is that Cumulus is closed at non-fixed times.
This morning too it happened around 05:20, then I unlocked it this morning at 09:00.
What I detected from the new Cumulus log is that there is a loss of wireless connection between the raspberry and my router; So this should be the problem. I solved it by changing the network to 5G. I attach a part of the log file where I found many failed attempts to connect to the home network.

From here I understood that the problem is with my network or with the RB, but I think it depends on the Raspberry because in 3 years of operation of the weather station on the Raspberry 3+ it had never happened to me!
However, I attach the screenshot of the /var/log/ folder because the syslog file is not there, while I see some boot.logs.
I therefore have to do further tests, I will let you know how the situation evolves. Thanks thanks thanks.
Roberto

[rogerthn]

Looks like bookworm, try

Code: Select all

sudo journalctl --since="2024-03-10 05:00:00"

Should show what happened this morning

[SamiS]

Thanks for the reply, here is the part of the log that describes what happened.
I specify that it refers to the new station that I am preparing on a new Raspberry 4. Thanks

I don’t know if it is anyhow related to CumulusMX shutting down unexpectedly, but your station logger interval is 30min and in CMX settings you have 5 min. Normally they should be identical.

[freddie]

Looking at the log, Cumulus is receiving the TERM signal so is being requested to shut down. Is Cumulus running as a service, or is it started from the command line? If as a service then there should be clues in the system log - accessible via journalctl as @rogerthn suggests. If it's from the command line then I'm not sure - shutting down will need some sort of manual intervention, such as hitting ctrl+c or perhaps closing the terminal window, or closing down a vnc session etc etc.

[rogerthn]

Maybe something in CumulusMX/MXdiags/ServiceConsoleLog.txt?

[rchi]

Here I am again! Sorry for the delay but I took some time to understand the reason for these senseless problems.
Then, I realized that a good part of them were due to the SD card which somehow wasn't making good contact in its slot . In any case I also preferred to change the Raspberry 4 with a new one and everything was fine. Now I just have to understand the reason for not seeing the Reports but this is another thing. I'll put up another post for this soon.
Thank you all so much for the suggestions and help you have given me. I hope to be able to reciprocate as soon as possible.
Roberto