Issue with 24hour rain picking up annual total on upgrade to 3213

[chrishudson]

I just upgraded from 3190 to 3213 and my 24hr rainfall and max24 hour rainfall showed as 747mm despite there being no rain on the day I upgraded and the day before. The 24 hour rainfall is increasing each day. 747mm was my total annual rainfall prior to the upgrade so it seems to have somehow picked up that figure. This has also impacted my this month, this year, monthly record for October, and all time record rain figures.

I have tried editing the monthly , yearly and all-time record 24hour figure and it immediately reverts back to the 747. I tried manually editing today.ini and yesterday.ini while CumulusMX was shut done and that immediately caused a mono crash, so had to revert to the backed up ini files.

The 747mm figure has now also made it into my SQL databases dayfile.

Is there a way I can remove that 747mm figure so it no longer jumps back into the data after editing the history data.

You can see below in my MXDiags my attempt to change the all-time figure and it immediately changing back.

Code: Select all

2022-10-30 17:40:00.491 DoLogFile: Writing log entry for 30/10/2022 5:40:00 PM
2022-10-30 17:40:00.498 DoLogFile: log entry for 30/10/2022 5:40:00 PM written
2022-10-30 17:40:00.531 Writing today.ini, LastUpdateTime = 30/10/2022 5:40:00 PM raindaystart = 747 rain counter = 747
2022-10-30 17:40:59.434 New all-time record: New time = 2022-10-30 15:30, new value = 154.200 "High 24 hour rain" prev time = 2022-10-30 15:30, prev value = 747.000
2022-10-30 17:41:00.479 New all-time record: New time = 2022-10-30 17:41, new value = 747.000 "High 24 hour rain" prev time = 2022-10-30 15:30, prev value = 154.200
2022-10-30 17:41:03.436 New all-time record: New time = 2018-02-26 07:10, new value = 747.000 "High 24 hour rain" prev time = 2022-10-30 17:41, prev value = 747.000
2022-10-30 17:41:41.893 FTP[Int]: Uploading daily graph data file: web/alldailytempdata.json

[chrishudson]

BTW The reason I did the upgrade was that I had a loss of data input and CumulusMX seemed to have auto-stopped. It took me 2 days to notice that it wasn't running. There were a series of escalating issues that seemed to start the day before the stoppage culminating in the loss of data input. I was hoping that somewhere in the upgrades between 3190 and 3213 this issue had been fixed.

To exacerbate issues there were no daily backups as they stopped over a month before [Sep 23rd] when an issue with HTTP uploads to WeatherCloud coincided with the daily backup process and it didn't happen. It then didn't happen on all the days since then. I only noticed this during the upgrade and my attempts to fix the spurious rain data.

I have attached the MXDiag file for reference.

[chrishudson]

Have determined the Mono crash happens when CumulusMX tries to send an email. In this case, it was when my rain total went above 25mm.
I tried to send a test email and that also generated the same crash.

Mono version is 6.8.0.105 running on a Rasberry Pi running Raspbian 5.15.61-v7 [bullseye]

Have attached MXDiag log, and Mono crash info. Also attached a screen shot that shows the rainfall chart dropped back to 0 after crash

[HansR]

Have determined the Mono crash happens when CumulusMX tries to send an email. In this case, it was when my rain total went above 25mm.
I tried to send a test email and that also generated the same crash.

Mono version is 6.8.0.105 running on a Rasberry Pi running Raspbian 5.15.61-v7 [bullseye]

Have attached MXDiag log, and Mono crash info. Also attached a screen shot that shows the rainfall chart dropped back to 0 after crash

See this thread (I point to the message where the solution is given).
So: update to mono 6.12!

[chrishudson]

Thanks, I had tried to update mono to see if that was the issue, but it told me I had the latest version. I followed the doco you linked and now am running Mono 6.12.0.182 and the crashes when sending email have stopped.

I have also been able to adjust my records now that the month has rolled over to a new month. [Although my monthlyalltime.ini had been cleared so I had to get that back from a previous days backup]

I did have an issue with Cumulus failing to terminate the first time running it after the Mono upgrade. It just sat there and didn't return to the prompt so had to close the terminal window to clear it. Last line in the MXdiags file was "Releasing mutex" which appears to be normal. Tried a couple more times and they closed without issue.

[HansR]

I did have an issue with Cumulus failing to terminate the first time running it after the Mono upgrade. It just sat there and didn't return to the prompt so had to close the terminal window to clear it. Last line in the MXdiags file was "Releasing mutex" which appears to be normal. Tried a couple more times and they closed without issue.

If you run it from the console CMX should not return to the prompt, it operates until you press ctrl-c. The console is meant to remain open.
If you want it otherwise you should run it as a service. Your profile says you are running Raspbian Stretch. It might be a good idea to upgrade that as well btw.

[chrishudson]

I do run CMX from a console. It was after hitting Ctrl-C that it didn't fully close.

Your profile says you are running Raspbian Stretch. It might be a good idea to upgrade that as well btw.

Fixed