I like to open the log file in a text editor and see if I can spot any obvious problems like dates missing. The other thing you can check is how many records are in the file. The file is written once per minute, so 60 X 24 = 1440 is the number of lines per day, then multiply by the number of days in the month to get the total. Check one of the files you listed as not complete and let us know what you find.
I’d be interested to hear how get on too, because I’ve had this exact same problem for many months since I started using WD in 2009 - for me it’s usually the last day or the last day’s graph that is missing, even on re-creation. I’ve never been able to find a reason why.
Seems to happen once or twice an hour (from just glancing at the file). I am going to take a look at my file to see if I have the same problem. Hopefully others will check there log files as well. Need to know if this is happening in the latest builds of WD.
Anyways, you can edit those files manually and remove the extra lines and then try to convert the log file and I suspect it will pick up the end of the month data correctly once you get the file length fixed.
Broadstairs has his online version at WD Log Checker and I ran the previously posted 102010lg.txt file through it. The page spit out a bunch of errors, but it did finally appear to process the file. It showed a bunch of errors in the file, ie.:
Error Description Record Contents
Timestamp does not increase (from 01 10 2010 00 03) in record 1 10 2010 0 3 10.0 85 07.6 1016.0 1 0 45 0.0 0.0 0.0 665.1 10.0
Timestamp does not increase (from 01 10 2010 00 05) in record 1 10 2010 0 5 10.0 86 07.8 1016.0 2 0 45 0.0 0.0 0.0 665.1 10.0
Timestamp does not increase (from 01 10 2010 00 11) in record 1 10 2010 0 11 10.0 85 07.6 1016.0 0 0 22 0.0 0.0 0.0 665.1 10.0
Timestamp does not increase (from 01 10 2010 00 21) in record 1 10 2010 0 21 10.0 86 07.8 1016.0 1 1 68 0.0 0.0 0.0 665.1 10.0
Timestamp does not increase (from 01 10 2010 00 26) in record 1 10 2010 0 26 10.0 86 07.8 1016.0 1 0 45 0.0 0.0 0.0 665.1 10.0
Timestamp does not increase (from 01 10 2010 00 35) in record 1 10 2010 0 35 10.0 86 07.8 1016.0 0 0 90 0.0 0.0 0.0 665.1 10.0
Timestamp does not increase (from 01 10 2010 00 44) in record 1 10 2010 0 44 10.0 86 07.8 1016.0 0 0 45 0.0 0.0 0.0 665.1 10.0
Timestamp does not increase (from 01 10 2010 00 55) in record 1 10 2010 0 55 10.0 86 07.8 1016.0 1 3 45 0.0 0.0 0.0 665.1 10.0
Timestamp does not increase (from 01 10 2010 01 04) in record 1 10 2010 1 4 10.0 85 07.6 1016.0 1 0 90 0.0 0.0 0.0 665.1 10.0
Timestamp does not increase (from 01 10 2010 01 14) in record 1 10 2010 1 14 10.0 85 07.6 1016.0 0 2 68 0.0 0.0 0.0 665.1 10.0
Timestamp does not increase (from 01 10 2010 01 17) in record 1 10 2010 1 17 10.0 85 07.6 1016.0 0 0 22 0.0 0.0 0.0 665.1 10.0
Timestamp does not increase (from 01 10 2010 01 23) in record 1 10 2010 1 23 10.0 85 07.6 1016.0 1 0 68 0.0 0.0 0.0 665.1 10.0
Timestamp does not increase (from 01 10 2010 01 35) in record 1 10 2010 1 35 10.0 85 07.6 1016.0 0 0 45 0.0 0.0 0.0 665.1 10.0
Timestamp does not increase (from 01 10 2010 01 52) in record 1 10 2010 1 52 09.9 86 07.7 1016.0 0 2 112 0.0 0.0 0.0 665.1 9.9
Timestamp does not increase (from 01 10 2010 02 01) in record 1 10 2010 2 1 09.8 86 07.6 1016.0 1 0 45 0.0 0.0 0.0 665.1 9.8
I do not know an easy way to edit out the duplicate entries…
Here’s something that might work…I ran your 102010lg.txt file through Websters DOS based checker and it creates an text file of the errors (see attached). Perhaps someone could write some code to use this file to make corrections to the file. It’s based on line numbers in the file, just read into an array all the line numbers, then delete those line numbers from the logfile.
If you can put the log files on your server and send me the links to the files I can run them thru the checker and email you the results file. Do you have some code that read the line numbers from the error file and delete those lines from the log file?