You’ll see in the sed regular expression that I change the : to a space, AWStats does not like having a : between the hostname and the port and I could find no way to making AWStats parse that correctly. I wrote little bash script that would take a file name, either (eg access.log or ) and would output that file after having parsed it to fix up the errors (later I discovered zcat -f will cat a file whether it is gziped or not so invalidating the need for the mycat function). Luckily the entries do include the actual URL that was requested so with a bit of grep and sed it was easy to reconstruct what the virtual host should have been. This presents another problem as you need to get them into order and normal alphabetical sorting does not work as there are no leading 0s in the file names.įurther, Apache was misconfigured and all the virtual host entries which should have indicated which virtual host was serving that access were in fact showing the ServerName.

The log files are rotated by logrotate and numbered access.log.1 access.log.2 access.log.3. My Apache logs are configured in the vhost_combined format which is one access.log file for all the virtual hosts. By default, debian sets AWStats up for a one domain host. As with all good open source software, the project is still there and ticking along.Ĭonfiguring AWStats turned out to be a but tricky. In fact I used to use it long ago before Google Analytics was available but I had forgotten about it. I had all the Apache logs for the period in question so it seemed a simple idea to put the data into something useful that would show charts to the client. I could not determine why it was not active when I am sure I set it up in the past. Upon investigating it turned out that for some reason the WordPress Google Analytics plugin was not active.

One of my clients had a problem where the last 6 months of data was not in Google Analytics.

Awstats apache log format