AWStats as the default stat package

Problem is, DA relies on webalizer for it's tallies I think.

I'd prefer if it just could drip webalizer as it's practically useless as a stats package IMHO and only supplies extremely minimal usable information.
 
agree awstats if setup correctly will not bring a server to its knees assuming decent hardware spec.
 
sullise said:
in: /etc/cron.d/directadmin_cron

Replace

PHP:
10 0 * * * root  echo 'action=tally&value=all' >> /usr/local/directadmin/data/task.queue

with

PHP:
10 0 * * * root /usr/local/directadmin/plugins/awstats/hooks/cgi-bin/awstats_updateall.pl now -awstatsprog=/usr/local/directadmin/plugins/awstats/hooks/cgi-bin/awstats.pl &&  echo 'action=tally&value=all' >> /usr/local/directadmin/data/task.queue

This way the awstats updates run before the webalizer and tally and log rolls..

...this doesn't actually work :( I've had it running for 5 days now, and the tally is updatet, whereas Awstats is not.

If I run ./awstats_updateall.pl all statistics get updated. However, the cron script doesn't update anything, and there aren't even any errors produced. Are you sure this is the correct script?

However, running /usr/local/directadmin/plugins/awstats/hooks/cgi-bin/awstats_updateall.pl now -awstatsprog=/usr/local/directadmin/plugins/awstats/hooks/cgi-bin/awstats.pl manually works fine. Is this an issue with my cron? Very strange though, considering tally is updated.
 
Last edited:
Sorry to hear it's not working for you. Works fine of us on 40+ servers daily.

I simply cut and paste the crontab from our servers. Be sure you entered it correctly.
 
I really don't know why. As I said, running it manually works fine, so there are no issues with the paths. It's crontab that's flawed, it seems. But I can't possibly see how.
 
Thanks sullise! I think I'll try to wipe every single Awstats file I have, and install it again, and hope it will do the trick. Since it's working for other people, it should work for me as well. I've simply been running upgrades of the Awstats plugin since it's first release, so things might have happened underway...

As most other people, I'd much prefer to get rid of webalizer and change it to Awstats altogether :)
 
IT_Architect said:
AWStats is the package web host customers are looking for. Webalizer is long out of date. cPanel guys gloat about having AWStats built in. The guys on the Plesk forum are furious about it because it was not in the new Linux/Unix version and there have been few who are successful adding it. That's the reason why I switched from Plesk to DA on the new server. DirectAdmin has a snapin but it doesn't install on FreeBSD without tinkering. If the snapin hadn't worked well, I wouldn't be here.

The absence of AWStats can easily be a deal killer for anyone with the potential to host commercial sites. There is no point in making it easy for the cPanels guys.

Awstats is not all that great. Any stats generating program that counts, you the admin and return clients everytime they come to your websites over the course of one day, is not a very accurate stats program. Urchin + UTM is a better option. If you can still get you hands on it that is.
 
Any application that you can no longer get youtr hands on, is de-facto, less useful than one you can.

People want AWStats, they dislike webalizer due to its output, Perhaps someone might like to update webalizer to produce graphics similar to AWStats, then things'd be different.
 
Re: Re: AWStats as the default stat package

pucky said:
Awstats is not all that great. Any stats generating program that counts, you the admin and return clients everytime they come to your websites over the course of one day, is not a very accurate stats program.

You can tell awstats to ignore your ip address.
 
2 of the most popular control panels have included AWstats into their choose list, cPanel has this feature for a long time, Plesk included it in the latest release (8.1). Why DirectAdmin can't have this feature in 2007 Q1 too?
 
Back
Top