Comments on: Webalizer - Apache web server log file analysis Tool

By: lol

lol — Thu, 08 Oct 2009 19:34:32 +0000

for multiple sites, set up a different config file and specify the hostname that you want displayed and the logs for each site, and then schedule a cron job to run with webalizer -c webalize-this-site.conf
You will also want to configure different output directories or subdirectories for each site so it doesn’t overwrite things.

By: Djoh

Djoh — Thu, 27 Aug 2009 12:05:00 +0000

To enable the apache2 hostname resolution is necessary ?

OMFG, what about the website performances ??? This is really bad idea…

By: gauri

gauri — Wed, 11 Mar 2009 06:46:32 +0000

whenever I run webalizer it shows:
Webalizer V2.01-10 (Linux 2.6.27-9-generic) locale: en_IN
Using logfile /var/log/apache2/access.log (clf)
Using default GeoIP database
Creating output in /var/www/webalizer
Hostname for reports is ‘bios-4′
Reading history file… webalizer.hist
Generating report for March 2009
Generating summary report
Saving history information…
670 records (660 ignored) in 1.00 seconds, 670/sec

But no new report is shown in the html pages..
why are the records getting ignored

By: John

John — Tue, 17 Feb 2009 04:28:11 +0000

Resolved.
Just in case someone in the future will be in same scenario as mine and have same problem. Change the Logfile directory from:

Logfile access.log (as mentioned above)

to Logfile …/site1/log/access.log
& Logfile …/site2/log/access.log

I also edit the …/sites-available/site1 and …/sites-available/site2 config file

on the line CustomLog, I point to the directory above.

in my case: CustomLog …/site1/log/access.log
and
CustomLog …/site2/log/access.log

restart everything and it works… Thanks for the howto page.

By: John

John — Sun, 15 Feb 2009 22:44:27 +0000

Hello Everyone,

I finally got a change to configure webalizer and Im running a little bit delema. Here is my scenario:
I’m running 2 websites (virtual server) on my ubuntu 8.04 server. both sites are already up and running http://www.johnlauder.com & http://www.statewideinvestors.com
My server hostname = server01.statewideinvestors.com

both sites have their own subdirectory …/site1/ & …/site2/
I have copied webalizer.conf together with access.log to …/site1/webstats/ & /site2/webstats/

I have also edited webalizer.conf on each site changing:
- Logfile access.log
- OutputDir …/site1/webstats (for 1st site webalizer.conf) & …/site2/webstats (for 2nd site webalizer.conf)
- Incremental yes
- HostName http://www.statewideinvestors.com (site1) & http://www.johnlauder.com (site2)

my problem, when i check the sites:
http://www.johnlauder.com/webstats ----> it shows server01.statewideinvestors.com
http://www.statewideinvestors.com/webstats ----> it also shows server01.statewideinvestors.com

I want it to show the individual site statistics NOT the server01 stats.

What I understand is, the HostName defines the report if specified (which I did) and I dont know why it is not doing it. I have also run webalizer and webalizer -q (which I think same effect <-- pls confirm it) on each site directory I have rebooted and restart server but no luck.

The other thing i dont understand is, when I ran Webalizer, It shows “Hostname for report is ‘www.johnlauder.com’” and “Hostname for report is ‘www.statewideinvestors.com’” respectively

Anything I miss? pls help. and thank you in advance

John

By: Rob

Rob — Wed, 12 Nov 2008 13:01:39 +0000

i forgot to write: : set this
LogFile /var/log/apache2/access.log

By: Rob

Rob — Wed, 12 Nov 2008 12:14:20 +0000

I was wrong, ignore the prev post.

the current log is not read when log is set to /var/log/apache2/access.log.1

So I think webalizer needs to be run before logs are rotated. To do so logrotate in /etc/cron.daily nust be run after webalizer . otherwise access.log could get rotated before webalizer processes it.
I think /etc/cron.daily scripts are in alphabetical order. so /etc/cron.daily/webalizer should be renamed to /etc/cron.daily/00webalizer , at least that is what I’ll try.

By: Rob

Rob — Tue, 11 Nov 2008 17:02:14 +0000

Hello
thanks for this page.

I did some tests and at least with Debian Etch and webalizer Version: 2.01.10-32 , the daily cron script check the current log when LogFile is set to /var/log/apache2/access.log.1

so this part could be changed above:

vi /etc/webalizer/webalizer.conf

## the cron script seems to check current log file always.
# this WILL get current and 1-st rotated log:
LogFile /var/log/apache2/access.log.1

By: lee.j

lee.j — Mon, 27 Oct 2008 07:44:14 +0000

Poor choice of Web stat applications. Webalizer is no longer in development and hasn’t been since 2002. AWstats would have been a more logical choice for this tutorial.

i have to disagree there, i have found it very powerful and returning exactly what i want.
as for awstats i found it over complex for a log display system.

By: ienabellamy

ienabellamy — Sun, 26 Oct 2008 10:11:21 +0000

i resolved: first i’ve say to virtual host to save the error log and the access log in dir of virtual host…and not on: /var/log/apache2/……

second: the second error: no valid records found, it’s because webalizer cannot create stats for an access.log WITHOUT ANY CONNECTION.

so, connect to your virtual host from a proxy, and after re-do sudo webalizer -q

By: ienabellamy

ienabellamy — Sat, 25 Oct 2008 21:44:18 +0000

Hello ! i followed all the tutorial, but when i do “webalizer -q” (with sudo) in the “logs” directory, i taken this error:
Error: Can’t open log file access.log

So, i had create a “touch access.log”, but the situations is this: “No valid records found!”

any helps ? thx

By: Scott

Scott — Fri, 29 Aug 2008 12:18:49 +0000

Webalizer was just updated in mid July 2008, the Ubuntu package will probably not be getting this update for a while. Any chance you woould be willing to tackle attempting to upgrade to the new tool? According to the readme, installing the new version is as easy as copying over the old release. That would be an interesting how to.

By: Jose Garcia

Jose Garcia — Tue, 08 Jul 2008 15:28:05 +0000

Lee is mistaken, and even it he were not, a good tool is valuable regardless of it’s development status.

By: Lee Dickey

Lee Dickey — Tue, 10 Jun 2008 13:21:38 +0000

Poor choice of Web stat applications. Webalizer is no longer in development and hasn’t been since 2002. AWstats would have been a more logical choice for this tutorial.