In launching my command:

/Usr/share/awstats/tools/awstats_updateall.pl now

And in doing so, subsequently :ps-efH

I noticed that the script /etc/cron.hourly/awstats was running.

I never created this script before, is it normal that the file /etc/cron.hourly/awstats either created automatically?

The biggest obstacle is that by running manually my command /usr/share/awstats/tools/awstats_updateall.pl now, in the end I found myself with two scripts awstats_updateall.pl that can be run simultaneously.

That's right, I can delete the script in /etc/cron.hourly/awstats but I want to know why this script was created alone.

Thank you

Most of your questions are answered in the AWStats Documentation (Installation, Configuration and Reporting) under sections II (Process logs: Building/updating statistics database) and III (Run Reports: Building and reading reports).

You can define a different DirData in each AWStats config file and the -dir option of awstats_buildstaticpages.pl allows to define the output directory for the generated static pages.

I have 3 conf files for which I would like to generate my results every day.
I'd like to use awstats.pl can access stats dynamics.

And
at the same time I like to use awstats_buildstaticpages.pl for static
pages are generated in a different directory for each file conf.

So I will wish to know the best method to use to generate dynamic pages and static.

I saw you could use the method awstats_updateall.pl now, is this the solution to generate dynamic pages?
How to generate static pages and redirecting the output to a different directory for each conf file?

Thanks

I'm so happy, thanks.

Well, even with this message, I believe that the log format is correct. Please check if the field separator is always just one space character. I suspect that there are 2 space characters between "Aug" and "2" in the beginning of the line (record 50 in the log file).

If this is the case, you should use :

LogSeparator="\s+"

in the AWStats config file.

Note that logresolvemerge  is able to merge log files with various dates and times, but it does not sort files. Each log file to be merged must be chronologically sorted.

I come back about my problem with my log format.

I use your LogFormat Jean-Luc: LogFormat = "%other %other %other %host %other %other %other %other %time1 %methodurl %code %bytesd %refererquot %uaquot"

And with this LogFormat, I have much corrupted records, so I use the option: -showcorrupted and here the out that I have:

Corrupted record (date 20100821095421 lower than 20100823062637-20000): Aug 21 09:54:11 12.XX.XXX.XX sco-log_access: 89.XX.XXX.XX - - [21/Aug/2010:09:54:21 +0200] "GET /images/titr_sco.gif HTTP/1.1" 200 1987 "http://site.fr/home.do;jsessionid=457A7420BBC3745CA1AF64DEE3E6BB20.sco-ddsco" "Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; GTB0.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; Media Center PC 5.0; SLCC1; Tablet PC 2.0; .NET4.0C)"

 

Corrupted record (date 20100821095421 lower than 20100823062637-20000): ...

Corrupted record (date 20100821095421 lower than 20100823062637-20000): ...

...

I'm sorry, sincerely because given your responsiveness, I would like a small fee but I don't decide.

My LogFormat  directive is correct because all logs are in the same format but I don't understand why with logresolvme.pl I have 0 corrupted records. Do you have an explication ?

Corrupted records are records that do not match the format specified in your LogFormat  directive. AWStats does not understand them and they are not in the reports.

To further debug your setup, you can use the -showcorrupted  option in the update command.

Another option is to ask us to check your configuration; this is a task we do for a small fee.

When I generate my stats with

awstats.pl -update -config=localhost

I have this result:

Jumped lines in file: 0
Parsed lines in file: 3303544
 Found 24 dropped records,
 Found 1652120 corrupted records,
 Found 0 old records,
 Found 1651400 new qualified records.

My question is:

What is the difference between the corrupted records et new qualified records ?

Does that mean I have 1652120 records that are not reflected in the outcome of my stats as they are "corrupted" ?

Is there a log file generated by awstats that would let me know why I have so many corrupted records?

I just try again but this time using logresolveme.pl and I have no records corrupted. I don't understand the logic, why with logresolveme I have no corrupted records?

Thanks

Thanks you for your help Jean-Luc.

This is not an error message. It is a normal output if your log files are very large. AWStats creates temporary files on the disk when performing the update.

This is, of course, more likely to happen when you merge log files to run an update that covers several days (or months). Another option is to separately run multiple updates one day (or one month) at a time. Always follow chronological order if you perform multiple updates.

I have a problem with my command:awstats.pl?config=localhost

Here the messages that appear in my terminal. I don't know the reason.

I verified my space disk but none disk is full.

Flush history file on disk (unique hosts reach flush limit of 20000)

Flush history file on disk (unique hosts reach flush limit of 20000)

Flush history file on disk (unique hosts reach flush limit of 20000)

Flush history file on disk (unique hosts reach flush limit of 20000)

...

Thanks