I have recently noticed that the daily BackupData routine only runs the first night after starting CMX. Subsequent nights the BackupData routine is not triggered. I turned Debugging on for a couple of days and have attached the resulting MXDiag file.
Does anyone else have this issue or is it unique to my setup?
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
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
[b3213] Daily BackupData routine only runs once after CMX restart
Moderator: mcrossley
-
chrishudson
- Posts: 22
- Joined: Sun 19 Jul 2015 5:37 am
- Weather Station: Davis Vantage Pro2
- Operating System: Raspbian Bookworm - Pi 5
- Location: Canberra, ACT
[b3213] Daily BackupData routine only runs once after CMX restart
You do not have the required permissions to view the files attached to this post.
- 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: [b3213] Daily BackupData routine only runs once after CMX restart
It looks like it is running ok...
Those two messages are output at the start and end of the backup process and no errors are flagged.
Code: Select all
2022-11-14 00:00:14.088 BackupData: Creating backup folder backup/daily/20221114000000/
..
2022-11-14 00:00:14.140 Created backup folder backup/daily/20221114000000/-
flort
- Posts: 248
- Joined: Thu 17 Dec 2020 9:06 am
- Weather Station: Davis Vantage Vue
- Operating System: Raspbian GNU/Linux 10 (buster)
- Location: Tin Can Bay, Queensland, Australia
Re: [b3213] Daily BackupData routine only runs once after CMX restart
It doesn't run for him on subsequent days. I've checked my log and it generates the backup at 5 seconds after midnight every day without fail.
- 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: [b3213] Daily BackupData routine only runs once after CMX restart
Ah, yes!
Very odd, I've tried to trace what is happening, but it's a bit tricky as so many processes, even so I cannot see a cause for this.
The CPU temperature stops being displayed after this entry...
That rPi is running hot!
The CPU temp is the last thing done the daily backup. But I cannot see anything in the log that indicates any sort of failure before the CPU temp is not run the following minute. The CPU temp code is in its own try/catch so if it fails it would output an error message to the log. As that is not happening it means the code isn't getting that far.
As an aside, the VP2 logger interval is set to 30 minutes, and CMX to 10 mins. That will cause a long delay at each start-up of CMX as it must process the entire logger contents each time.
Very odd, I've tried to trace what is happening, but it's a bit tricky as so many processes, even so I cannot see a cause for this.
The CPU temperature stops being displayed after this entry...
Code: Select all
2022-11-14 09:06:01.197 Current CPU temp = 84.9°CThe CPU temp is the last thing done the daily backup. But I cannot see anything in the log that indicates any sort of failure before the CPU temp is not run the following minute. The CPU temp code is in its own try/catch so if it fails it would output an error message to the log. As that is not happening it means the code isn't getting that far.
As an aside, the VP2 logger interval is set to 30 minutes, and CMX to 10 mins. That will cause a long delay at each start-up of CMX as it must process the entire logger contents each time.