| 5:56 am on Sep 26, 2006 (gmt 0)|
I noticed that all the webstat programs froze in time Sept. 17 & 18 on all my websites. I thought it was an issue with my webhost servers. Sites are on 2 different servers. My webhost installed the Awstat update button and I can now get updated stats on that but the other (Analog&Webalizer) stats still aren't working.
| 8:30 am on Sep 26, 2006 (gmt 0)|
Have you tried using the update-all script for awstats? I use it in my crontab without problems to update stats every hour for about 10 sites. It could also be a rights problem. Under which user is the crontab line executed? Maybe this user doesn't have rights to access the log files or store the results in a file.
My crontab line:
5 0-2,6-23 * * * username nice /usr/local/awstats/tools/awstats_updateall.pl now > /dev/null 2>&1
| 8:35 am on Sep 26, 2006 (gmt 0)|
Thanks for the reply, I have set the crontab using Admin.
Would the one you suggested go in one place or on each domain?
| 10:41 am on Sep 26, 2006 (gmt 0)|
I have this line in the central /etc/crontab file. The awstats_updateall.pl script scans all config files in your /etc/awstats directory (or where you store them) and processes the config files for each site.
Please note the nice statement in front of the call to the perl script. This causes the script to run at low priority which improves the performance of your site(s) during the statistics update. Processing the statistics may take a few seconds longer because of this, but users of your site will have faster response times when the scripts runs in the background during their site visit.
| 6:21 am on Sep 27, 2006 (gmt 0)|
Ok, just set the following crontab as root (not domain):
5****/usr/local/awstats/wwwroot/cgi-bin/awstats.pl -config=www.domain.com -update
To test if it will update every 5 minutes ... still not doing it.
I cant do the update-all option since there are a bunch of other sites on the server that are not mine, I just have one account with about 25 domains (not all of them need stats).
| 8:18 pm on Sep 27, 2006 (gmt 0)|
Yo can run awstats.pl from the command line. Try it that way and see if the script generates an error. If it gives some statistics about the number of lines processed, you know it is working. Then you can concentrate on getting it to work in your crontab.
| 6:33 am on Sep 28, 2006 (gmt 0)|
Got it working!
It needed the crontab at the root level AND domain level.
No idea why, but I'm glad its solved.