I installed AWStats on CentOs 5.0. It uses to analyse Apache Logs & Â Window IIS 6.0 Logs.
Â
Only apache on CentOs 5.0 is working properly.
When i tried to analyse the IIS Log,it throw out error message
Error: Your personalized LogFormat does not include all fields required by AWStats (Add %bytesd in your LogFormat string). Setup ('/etc/awstats/awstats.kaplan.com.sg.conf' file, web server or permissions) may be wrong. Check config file, permissions and AWStats documentation (in 'docs' directory).
As indicated in the error message, there is no %bytesd field in your log format. The %bytesd  field (called sc-bytes by IIS) is mandatory.
Â
Here is what you can do with existing log files: : you can fool AWStats by calling %bytesd one of the unused fields at the end of the line. You can try this:
I thought my previous answer showed the difference between ex%YY%MM%DD and ex%YY-24%MM-24%DD-24.
"-24" means "now minus 24 hours", "-37" would mean "now minus 37 hours", if there is no "- something", than the datestamp for today ("now") is used.
Â
I have never seen this "First visit: not available" message. It is weird, it looks like an AWStats bug.
You are right: it is not a "message", but IÂ understood what you mean with the Summary at the top.
Â
If it is a bug in AWStats, you have to report it in the AWStats Bugs Trackers. I don't see this "First visit: not available" as an important issue though.
I guess that your IIS logs are showing GMT time while the Linux system is showing the Hong Kong local time. This can explain the 8 hours difference. It is not really an error, but a different way to present the data.
The timezone plugin does not change the data which are already in the AWStats database, as it recalculates all dates and times when running the AWStats updates.
You can do that, but I would first move the existing AWStats database to another directory (just in case). Then you enable the plugin and rerun the stats updates from the beginning and you will get the stats based on the time zone of your choice.