CreateMissing - strange error

[Defenderdogs]

I am getting around to cleaning up my Weatherlink history and have recreated the monthly files. I ran CreateMissing and noticed an error when processing 201601log.txt, telling me that "No Monthly Data was found". Looking at the log file I notice something a little odd in that it seem to be processing 201601log.txt, but on the next line references 201602log.txt. This was just a test run after adding the Jan16 file, the Feb16 file doesn't yet exist which I am sure explains the error, but what am I doing wrong to make it look for that file in the first place? Log file snippet here....

2024-11-28 13:39:09.070 Date: 01/02/2016 : Adding missing data
2024-11-28 13:39:09.083 LogFile: Finished processing log file - /root/CumulusMX/data/201601log.txt
2024-11-28 13:39:09.084 LogFile: Log file not found - /root/CumulusMX/data/201602log.txt
2024-11-28 13:39:09.084 LogFile: Finished processing all log files
2024-11-28 13:39:09.084 01/02/2016 : No monthly data was found, not updating this record
2024-11-28 13:39:09.084 Date: 01/03/2016 : Adding missing data
2024-11-28 13:39:09.097 LogFile: Finished processing log file - /root/CumulusMX/data/201601log.txt
2024-11-28 13:39:09.097 LogFile: Log file not found - /root/CumulusMX/data/201602log.txt
2

[mcrossley]

Could you post the whole log file please.

But CreateMissing will normally run the processing from the start date until the current date.

[Defenderdogs]

Log attached - I just ran it again. It's running against the log files already in the data directory, just the 201512log.txt file is new; I wanted to test it against the newly created file before replacing all the existing one and the dayfile entries.

[mcrossley]

I'll park this one until I get the next CMX release out. I've logged it in my Todo list

[Defenderdogs]

So it's not me and there's an issue somewhere?

[mcrossley]

Possibly, I haven't looked into it. But it would appear to be a benign error, when no data is found in the log file it is supposed to be in, CM is not stopping soon enough and rolling through to the next log file.

[Defenderdogs]

But there are data in the log files. Here's the first few lines of 201512log.txt (record start date is 2015-12-13) and each subsequent log file has a full month of data. I thought it might be a permission problem but they set the same as all the other files in the folder.

13/12/2015,12:00,6.5,94,5.6,0.0,1.6,,0.0,0.0,1016.1,0,18.8,56.0,1.6,6.5,6.6,0,0,0.0,0,6.6,0,0,,0,0.0,6.6,0
13/12/2015,12:30,6.5,95,5.8,1.6,6.4,90.0,2.0,0.5,1015.8,0,18.1,57.0,6.4,6.5,6.6,0,0,0.0,0,6.6,0,0,90.0,0,0.5,6.6,0
13/12/2015,13:00,6.7,95,5.9,3.2,6.4,112.5,0.0,0.3,1015.6,0,17.8,57.0,6.4,6.7,6.8,0,0,0.0,0,6.8,0,0,112.5,0,0.3,6.8,0
13/12/2015,13:30,6.8,96,6.2,3.2,9.7,112.5,0.0,0.0,1015.4,0,17.8,57.0,9.7,6.8,7.0,0,0,0.0,0,7.0,0,0,112.5,0,0.0,7.0,0
13/12/2015,14:00,6.9,96,6.4,3.2,6.4,90.0,0.0,0.0,1015.1,0,17.7,57.0,6.4,6.9,7.1,0,0,0.0,0,7.1,0,0,90.0,0,0.0,7.1,0
13/12/2015,14:30,7.0,96,6.4,3.2,6.4,112.5,0.0,0.0,1015.0,0,17.6,57.0,6.4,7.0,7.1,0,0,0.0,0,7.1,0,0,112.5,0,0.0,7.1,0
13/12/2015,15:00,7.1,96,6.5,3.2,6.4,90.0,0.0,0.3,1015.0,0,17.6,57.0,6.4,7.1,7.2,0,0,0.0,0,7.2,0,0,90.0,0,0.3,7.2,0
13/12/2015,15:30,7.1,96,6.5,3.2,6.4,90.0,0.0,0.0,1015.0,0,17.5,57.0,6.4,7.1,7.2,0,0,0.0,0,7.2,0,0,90.0,0,0.0,7.2,0
13/12/2015,16:00,7.2,97,6.8,3.2,6.4,90.0,0.0,0.3,1014.9,0,17.4,57.0,6.4,7.2,7.4,0,0,0.0,0,7.4,0,0,90.0,0,0.3,7.4,0
13/12/2015,16:30,7.3,97,6.9,3.2,6.4,90.0,1.3,0.3,1015.0,0,17.4,57.0,6.4,7.3,7.5,0,0,0.0,0,7.5,0,0,90.0,0,0.3,7.5,0
13/12/2015,17:00,7.4,97,7.0,3.2,6.4,112.5,0.0,0.0,1014.9,0,17.3,57.0,6.4,7.4,7.6,0,0,0.0,0,7.6,0,0,112.5,0,0.0,7.6,0
13/12/2015,17:30,7.5,97,7.1,1.6,6.4,112.5,0.0,0.0,1015.0,0,17.3,57.0,6.4,7.5,7.7,0,0,0.0,0,7.7,0,0,112.5,0,0.0,7.7,0

[packman2008]

Try changing instances of ,, (comma comma) to , , (comma space comma). The standard log file documentation isn't clear on this, but I found one of my logfiles didn't process nicely until I added the spaces.