#AWSTATS ERROR.LOG WINDOWS#

Then, AWStats continues its work (if configured as cron job) and updates the statistics from the formerly offending point on. Before you should stop the webserver (e.g., service apache2 stop) and afterwards start it again ( service apache2 start). However, if more than 50 of that kind happen to occur without a break, AWStats stops working completely from this point on and for the future (exactly: until the log file is exchanged).Īs a remedy, one can delete the lines in question from the log file (at least so many that less that 50 remain consecutively). Such entries are appearing from time to time in webserver log files and are no problem normally. (where stands for a concrete IP address) as invalid. '-' 408 1447 '-' '-'Īpparently, AWStats evaluates log-file entries with blank fields as

#AWSTATS ERROR.LOG WINDOWS#

'GET / HTTP/1.1' 200 1234 '' 'Mozilla/4.0 (compatible MSIE 5.01 Windows NT 5.0)'Īnd this is an example of records AWStats found in your log file (the record number 50 in your log): This means each line in your web server log file need to have 'combined log format' like this: Your log file /var/log/apache2/ssl_access.log must have a bad format or LogFormat parameter setup does not match this format. I have changed the root users name (if this is important).

And the log files: var log virtualmin the owner is: www-data:www-data and the permission is: 0660. In the: publichtml awstats index.html the owner is: example:example and permission is: 0664. Error Logs This feature displays the last 300 errors that have occurred on. Check config file, permissions and AWStats documentation (in docs directory). Where stands for the configuration in question, results in an error message likeĪWStats did not find any valid log lines that match your LogFormat parameter, in the 50th first non commented lines read of your log. AWStats Displays information about who is accessing your website. The following situation arises (for me the first time after years of usage): AWStats runs by crontab, but all of a sudden no statistics are generated anymore an error related to the execution of crontab can be ruled out.

Awstats error.log