Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I've setup AWStats on my VPS to get some more insight into the traffic coming to my site. As instructed I ran a manual build/update which ran fine:

sudo -u www-data ./awstats.pl -config=xxxx.com

Create/Update database for config "/etc/awstats/awstats.xxxx.com.conf" by AWStats version 6.9 (build 1.925)
From data in log file "/usr/share/doc/awstats/examples/logresolvemerge.pl /var/www/xxxx.com/logs/*-access.log |"...
Phase 1 : First bypass old records, searching new record...
Searching new records from beginning of log file...
Phase 2 : Now process new records (Flush history on disk after 20000 hosts)...
Warning: awstats has detected that some hosts names were already resolved in your logfile /usr/share/doc/awstats/examples/logresolvemerge.pl /var/www/xxxx.com/logs/*-access.log |.
If DNS lookup was already made by the logger (web server), you should change your setup DNSLookup=1 into DNSLookup=0 to increase awstats speed.
Jumped lines in file: 0
Parsed lines in file: 814
 Found 0 dropped records,
 Found 0 corrupted records,
 Found 0 old records,
 Found 814 new qualified records.

It also produced the file in the DatDir: /var/lib/awstats/awstats052010.xxxx.com.txt which contains what I would expect.

BUT when I visit: xxxx.com/awstats/awstats.pl it tells me

Last Update:  Never updated (See 'Build/Update' on awstats_setup.html page)

and the rest of the page is blank. I'm pretty sure I set it up correctly but now I cannot figure out why this is happening. Hopefully someone smarter then me can help me.

Thank you in advanced.

share|improve this question
    
With blank I did not mean blank but an AWStat page without any stats . Sorry for the possible confusion. –  user42260 May 5 '10 at 7:56

1 Answer 1

Two possibilities.

Either the permissions of the file created when you run awstats are not set to allow your webserver to read the files, i.e. they are owned by a user other than www-data and have permissions of 640.

or

The regexp is set so that the hostname is expecting the URL to be domain.com and you are visiting www.domain.com (less likely based on the fact that your sudo -u www-data method worked)

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.