Running AWstats is helpful for finding simple information and I think it does a okay job in identifying robots. Last week I installed xampp onto a Windows server to allow me to process the old log files from my Apache server. These files date all the way back to 2002. It took me a bit of time but I figured out how to:

  1. Get AWstats working with xampp
  2. Modify the changes needed for getting AWstats working
  3. Configure a profile to have AWstats process historical records
  4. Monitor its progress

First step - Install xampp

I am not going to put any details in here because I think this is pretty easy todo. I will say, you should visit your http://localhost/xampp/security page to ensure your site is secure.

Installing AWstats

I dropped my AWstats directory into my root install of c:\xampp and copied the files of c:\xampp\awstats\wwwroot* to the path of c:\xampp\htdocs\awstats Then created a new file in c:\apache\conf\extra\awstats.conf with the following code:

    Alias /awstats/classes "c:/xampp/htdocs/awstats/classes"
    Alias /awstats/icon "c:/xampp/htdocs/awstats/icon"
    Alias /awstats/css "c:/xampp/htdocs/awstats/css"
    ScriptAlias /awstats/cgi-bin/ "c:/xampp/htdocs/awstats/cgi-bin/"
    <directory c:>
    Options ExecCGI

Add the following line in your c:\xampp\apache\httpd.conf:

    Include extra/awstats.conf

Save and relaunch Apache to check your changes are correct before continuing.. well, you dont have to, but I recommend it to avoid debugging.

Building a AWstats profile

I copied an existing file from AWstats directory and made my own with some small changes:

    Logfile="c:/xampp/perl/bin/perl.exe c:/xampp/awstats/tools/logresolvemerge.pl c:/path/to/log/files/access_log.200201* |"

Processing log files

To begin your processing of the log files:

    c:\xampp\perl\bin\perl.exe c:\xampp\htdocs\awstats\cgi-bin\awstats.pl -config=name_of_conf -update -debug=3

I use the -debug=3 because it can take a long time to process the log file and I like knowing what is going on. Good Luck!

comments powered by Disqus