poltandroid.blogg.se

Awstats error.log
Awstats error.log









awstats error.log

Such rule makes two hits into log files, so most log analyzer count them twice, but only one page were “viewed”.

#AWSTATS ERROR.LOG DOWNLOAD#

This decrease the error, not completely, because it’s always possible that a proxy server download one HTML frame and another one download another frame, but this make the over-reporting of unique visitors less important.ĪWStats does not count twice (with default setup) redirects made by server “rewrite rules”. So AWStats considers only HTML “Pages” to count unique visitors. Because of this, if stats of unique visitors are made on “hits”, 3 users are reported but it’s wrong.

awstats error.log

This is a very bad way of working : Some visitors use a lot of proxy servers to surf (ie: AOL users), this means it’s possible that several hosts (with several IP addresses) are used to reach your site for only one visitor (ie: one proxy server download the page and 2 other servers download all images). Some log analyzers use the “Hits” to count visitors. However AWStats is one of the most accurate and its “over reporting” is very low where all other analyzers, even the most famous, have a VERY HIGH error rate (10% to 200% more than reality !). In fact, all analyzer (even AWStats) make “over reporting” because of the problem of proxy-servers and robots. If you compare AWStats results with an other log file analyzer, you will found some differences, sometimes very important. to get the logs from there use the following command.

awstats error.log

if you use centos 7 /var/log/audit/audit.log is replaced by journald. semodule -i httpdawstats.pp activates that policy.

I rather think the problem should be somewhere here (clicks or rewrites?): audit2allow -m httpdawstats < EOF creates a selinux policy.

But I don’t think that the problem are the different bots / user agents.











Awstats error.log