Web Hosting Talk







View Full Version : webalizer.conf stopped working (in cpanel environment)


Jeffy
09-22-2005, 08:52 AM
I am using webalizer on a cpanel-based shared hosting server.
(Linux 2.4.31, Apache/1.3.33, WHM/cPanel 10.6.0-RELEASE 201, Webalizer 2.01)

I am using a custom webalizer.conf file for each of my sites on that server. That file is located at
/home/myacct/webalizer.conf

My custom webalizer.conf files worked fine for months and months, until...

Around the beginning of September, the nightly webalizer run stopped using my custom webalizer.conf file. Now I just get the generic version. My provider tells me they "loaded the latest cpanel security patches" around the time it stopped working.

Any ideas? Has the location for the file been changed? Does anybody know the name of the cpanel script that runs webalizer and points it at the account's custom webalizer.conf ? If I knew the script name, maybe I could get my provider to compare the script before and after.

(I have only whm, cpanel, ftp access to the server ... no shell login)

Thanks for any help.
-Jeff

Jeffy
09-22-2005, 12:11 PM
Some additional information:

I have found that at one time, the script was called
/usr/local/cpanel/cpanellogd
and the pertinent part looked like this:
-------------------------------
if (-e "$homedir/webalizer.conf") {
logsystem("$root/bin/logrunner ${cpunum}.0
$root/3rdparty/bin/${weblang}webalizer -c $homedir/webalizer.conf -N 10 -D
$homedir/tmp/webalizer/dns_cache.db -R 250 -p -n ${access_log_name}
-o $homedir/tmp/webalizer ${waccess_log}");
} else {
logsystem("$root/bin/logrunner ${cpunum}.0
$root/3rdparty/bin/${weblang}webalizer -N 10 -D
$homedir/tmp/webalizer/dns_cache.db -R 250 -p -n ${access_log_name}
-o $homedir/tmp/webalizer ${waccess_log}");
}
---------------------------------
but now support at my provider tells me there is no longer any reference to "$homedir/webalizer.conf"
in the script that runs the webalizer

Jeffy
09-27-2005, 08:53 AM
Found the answer:

A recent update to cPanel has changed where webalizer is sent to look for the user's custom webalizer.conf file.

The old location was $homedir/webalizer.conf

The new location is the same folder as webalizer's output:
$homedir/tmp/webalizer/webalizer.conf

Not sure if the change was intended or inadvertent.