Re: [cobalt-users] Site name change causing havoc with Webalizer stats

[johan@xxxxxxxxxx]

>>>
The first thing to do is to find out where Webalizer is picking up the site
name.  If you installed from the Cobalt-aid.sourceforge.net Webalizer 2.01
package, the name is take from the name on the symbolic link in the /home/sites
directory.  The script that does this is /usr/bin/webalizer2.pl and you would be
looking at the variable $asite as it is passed into the -n option on the
webalizer command.
>>>

None of the above, but thanks anyway.  The problem would have sorted itself out
within a day or two ...  Reason being that we've moved webalizer to the front of
the crontab queue (awebalizer), and it was running before the actual stats for
the day was added to the web.log file in the /home/sites/sitexyz/logs directory
- very, very silly indeed ;-)

Webalizer was run manually to get things going, but only after the web.log file
was cleared of older data (the test site did not attract much traffic, and the
log file hasn't been rotated yet).  

I should've done more homework before posting, but it was just a very busy week.
The site in question was moved from an Adgrafix (aka Hosting.com) server (a Sun
Solaris box), which was down for more than 36 hours (starting on Monday).  They
eventually had to move all sites to another server ...

rgrds,

Johan

http://host24.com






---------------------------------------------
This message was sent using M-Web Airmail.
http://airmail.mweb.co.za/