Hello,
Firstly, if you type “webalizer”, and you see the following:
server1# webalizer Webalizer V2.01-10 (FreeBSD 6.2-STABLE) English Using logfile STDIN (clf) Creating output in current directory Hostname for reports is 'server1.*.be' History file not found...
then your binary is working fine, don't recompile
DirectAdmin doesn't just run “webalizer”, it runs a whole series of command line options to tell webalizer what to do. Just running “webalizer” only tells us that it's there, is responding and should work when DA calls it.
Possible causes of not seeing any webalizer stats: - the most common, crond not installed/working, thus preventing the task.queue from being processed, in turn preventing tallies/stats updates:The task.queue is not being processed
- if the task.queue is being processed, then make sure that your domains actually resolve to your sever. Webalizer needs something to work on.
Check:
/var/log/httpd/domains/domain.com.log
to ensure that it's being filled with log data. If not, either the domain doesn't resolve there, or maybe the CustomLog option is not in your virtualhost in your httpd.conf file.
- a less common cause is if the use is not present in his creators users.list file, so DA doesn't know he exists, thus he doesn't get tallied.
Check:
/usr/local/directadmin/data/users/creator/users.list
where creator can be admin, or the name of the reseller that created the user.
- Make sure the webalizer binary is in the correct spot:
Freebsd: /usr/local/bin/webalizer
Debian/Redhat: /usr/bin/webalizer
- If you get weird binary errors when you run “webalizer” (and you don't see the above output), then before trying to recompile, you'd want to download a new binary
They're all from http:files.directadmin.com/services in the related OS folder.
- If you still get binary errors, even after downloading a new binary, then it's possible the binaries just dont get along with your system. You can either use a package system like “yum install webalizer” to install it, or compile your own with the build script. Note that the build script only compiles webalizer if the binary does not exists, so if you've got a broken binary there, delete it first before running ”./build webalizer”.
- the least common problem, but that has happend is when the admin tries to get too fancy with the custom templates and breaks webalizer. If you have: /usr/local/directadmin/data/templates/custom/webalizer.conf try deleting it, then run the tally again. It's likely you've added an option that webalizer chokes on.
That about covers all possible things that can prevent you from seeing your webalizer stats