InternetOfficer.com

Hi,

The message you get at the end of the update does not show any error, but the "LastLine in future" warning. This pointless warning can disturb the reports. I would remove it by commenting out lines 10174 to 10178 in awstats.pl  (6.9).

Two more questions if this does not solve the problem :

• Are you dynamically generating the reports (.pl) or are using static reports (.html) ?
• Are the AWStats database files created in the DirData  directory ?

Please paste here the DirData  line from your AWStats confilg file.

The AWStats report is dynamic if its URL contains awstats.pl  and it is static if the URL ends with .html .

This is weird.

When I try to run an update with DirData pointing to a write-protected DirData  directory, I get :

And when I try to run an update with DirData  pointing to a directory that does not exist, I get :

As AWStats first writes a temporary data file in DirData , it needs to read it back to generate the final data file. I do not see how it could be doing that without detecting when DirData  does not exist or when it is write protected.

In your first post, you wrote :

WARNING: LastLine parameter in history file is '20090601165415' so in future.
(…)
Direct access after last parsed record (after line 39142)

Then you wrote :

the dirdata directory doesn't have any files at all i dont know why it wont create the files ?

That does not make sense !

The date stamp of the LastLine parameter and the "last parsed record" mentioned in your first post have been read by AWStats in an existing data file in the DirData directory. Your statement that there is no file in the DirData  directory cannot be true.

Maybe you or another application erased the AWStats files in the DirData  directory or you looked in the wrong directory. Note that, in case there are several definitions of DirData  in the AWStats config file, only the last one will apply.

Hello,

You now get “Found 7199 already parsed records“. AWStats found these 7199 already parsed records in its data files in DirData . Thus it is clear that the database has been updated.

What you describe could happen, if you do not use the same AWStats config file when updating and when calling AWStats from the browser. The address in the address bar of your browser should be like this :

(assuming awstats.x.com.conf is the config file as in the update command).

I cannot tell if you have to use the old or the new config file, as I do not know what the differences are between the two.