Page 1 of 1
Rain not logged
Posted: Tue 05 Mar 2024 12:39 pm
by Matt.j5b
After the rollover on 1 Mar CMX no longer is logging new rainfall.
In the diags I get: "DoRain: A reading arrived at the start of a new day, but before we have done the roll-over. Ignoring it". I can see in the diags file the roll over occurs for the new day before this but I get new entry gets added to the dayfile for the previous and nothing else suggests the roll over didn't occur.
I rewound the data back to before 1 Mar thinking that might help but the issues occurs right thorough the whole catch-up period instead (28 Feb to now). This wasn't showing up in the diags (and rain was being recorded correctly) until the 1 Mar.
Attached is the diag for the data rewound.
Thanks in advance.
Re: Rain not logged
Posted: Tue 05 Mar 2024 1:21 pm
by Matt.j5b
To add when I rewind the data I notice in the today.ini file once the re-wind is completed doesn't change to current date and instead stays the same.
By that, this is the top bit of the today.ini after the re-wind is complete.
Code: Select all
#Last updated: 05/03/2024 23:15:49
[General]
Date=05/03/2024
Timestamp=2024-03-05T23:10:00
CurrentYear=2024
CurrentMonth=2
CurrentDay=29
Maybe that is something got to do with CMX thinking that the data is for the new day before the roll-over is completed.
Re: Rain not logged
Posted: Tue 05 Mar 2024 3:44 pm
by mcrossley
There is something wrong with your dayfile...
Code: Select all
2024-03-05 22:24:15.993 LoadDayFile: Attempting to load the day file
2024-03-05 22:24:16.018 ParseDayFileRec: Error at record 2 - Input string was not in a correct format.
2024-03-05 22:24:16.019 LoadDayFile: Error at line 1 of data/dayfile.txt : Error at record 2 = "" - Input string was not in a correct format.
2024-03-05 22:24:16.025 Please edit the file to correct the error
2024-03-05 22:24:16.027 ParseDayFileRec: Error at record 2 - Input string was not in a correct format.
2024-03-05 22:24:16.027 LoadDayFile: Error at line 2 of data/dayfile.txt : Error at record 2 = "" - Input string was not in a correct format.
2024-03-05 22:24:16.028 Please edit the file to correct the error
2024-03-05 22:24:16.028 ParseDayFileRec: Error at record 2 - Input string was not in a correct format.
2024-03-05 22:24:16.028 LoadDayFile: Error at line 3 of data/dayfile.txt : Error at record 2 = "" - Input string was not in a correct format.
2024-03-05 22:24:16.029 Please edit the file to correct the error
... etc
Take a look and see if you can spot the problem, otherwise post your day file for me to take a look at it.
Re: Rain not logged
Posted: Wed 06 Mar 2024 12:07 pm
by Matt.j5b
That is because I have nulls from including data prior to starting with Cumulus. I know you are not supposed to include nulls as CMX can't load the dayfile properly but it is there because there was significant weather that occurred during that time.
This issue seems to be related to the today.ini being stuck on 29 Feb. I have manually changed the wrong date to the correct day and on roll-over the date updates correctly. I don't get any of the DoRain error messages now.
Re: Rain not logged
Posted: Wed 06 Mar 2024 2:29 pm
by mcrossley
If Cumulus cannot load the day file, then all sorts of things will go wrong. It needs to be fixed.
Re: Rain not logged
Posted: Thu 07 Mar 2024 12:11 pm
by Matt.j5b
Yes I fully understand it create problems but it would be a major disadvantage to remove about 2 years of data before I used Cumulus for the reason that CMX can't handle nulls. This data is not complete enough to not have nulls so I would need to completely remove the data from the dayfile. I have some content on my website that reads the dayfile directly instead of using mysql that add benefit from including this extra data. I plan to change those to use mysql instead, at which point I could remove the offending data from the dayfile.
I know a lot of the functionality in the CMX dashboard interface don't work properly for me because of this. I am not bothered by that as I use my website for looking at the data anyway.
It doesn't seem to have an impact in writing the data to the file with the impact appearing to be limited to the CMX interfacing reading the dayfile for the features I don't use.
But for the issue I experienced with CMX getting stuck on the leap day and also going by the other thread with the same issue:
viewtopic.php?t=22017 it appears that this is not related to the dayfile as that correctly wrote for each day after the leap day, albeit with no rainfall totals.
Re: Rain not logged
Posted: Thu 07 Mar 2024 2:50 pm
by mcrossley
Leaving the dayfile and the issues that will cause for now...
The problem is being caused by the today.ini file, which when CMX reads it:
Code: Select all
2024-03-05 22:24:15.879 ReadTodayFile: Last update time from today.ini: 28/02/2024 20:00:00
2024-03-05 22:24:15.880 ReadTodayFile: Date = 05/03/2024, LastUpdateTime = 28/02/2024 20:00:00, Month = 2
Is saying that the last data update was 28/02/2024, but the file was last updated 05/03/2024.
If you set the general date/time back to 28 Feb, it should catch-up correctly, unless there are further problems it hits.
Code: Select all
[General]
CurrentYear=2024
CurrentMonth=2
CurrentDay=28
Re: Rain not logged
Posted: Fri 08 Mar 2024 12:22 pm
by Matt.j5b
Thanks for confirming this.
Strangely, rewinding back to 28 Feb (and also changing the timestamp) didn't work for the current date in today.ini to update correctly.
CMX would still catch-up the data but today.ini would stay at 28 Feb with the consequence with the rainfall not getting logged. I changed the current date manually afterwards to the current date and had since roll-over properly for a few days now.