I've got the awstats[MM][YYYY].domain.txt files going back to July 2008. A problem means I'm missing between 27th Dec 2008 and 6th April 2009.
Having read about my problem I removed this month's file believing awstats would see the last stats file was 122008 and would parse the log file (that I've generated in the format specified in the config file for that period) and write new stats for 27th Dec onwards.
My problem is that the in log file I'm giving it contains approx 22000 records, it jumps 21500 of them and just adds the stats for the last 24 hours or so.
The only reference to the LastLine it's processed I could find is in the stats files, so I changed that to match the last record:
BEGIN_GENERAL 8
LastLine 20090406142201 21431 2574944 27607447828
FirstTime 20081201001045
LastTime 20081226235701
LastUpdate 20090417163025 1 0 0 0 0
changed to
BEGIN_GENERAL 8
LastLine 20081226235701 21431 2574944 27607447828
FirstTime 20081201001045
LastTime 20081226235701
LastUpdate 20081226235701 1 0 0 0 0
but I assume this is not the only record of the last record it keeps as if I run the update again with these changes, it still jumps the ~21500 records and writes the few hundred records for April to a new stats file.
Does anyone know where awstats keeps the critical date/time that is stopping the stats updating for the missing period?
Any help gratefully received!
jc