Webalizer

[NMS]

Webalizer cron tutorial for customization purposes:

http://help.powweb.com/tutorials/webstat/setup.php

[NMS]

Seems that I managed to update my Awstats with cron. I am going to verify this in the next hour and if it works I will post the link for the tutorial.

FINGERS CROSSED.

[NMS]

Awstats Cron Tutorial:

http://www.help.powweb.com/tutorials/webstat/awcron.php

Enjoy!

[Roy]

Hey Nev,

This is exactly the same crontab text I tried several month ago - without success. What's changed? Is it still working? PowWeb must have changed something for it to work.

I already have it in my crontab file. All I have to do to try it again is remove the # from in front of the line it is on. I'll give it another go. I do hope it does work. Every now and then, I forget to update AWStats manually on a daily basis and when I do get to it ends up being too large to do so. Then I have to do it manually at the end of the week from the zipped file.

Do you still have WebStats turned on? Do you anticipate any problem at the end of the week with AWStats updating and access_log zipping?

Let's hope, we have something here.

Cheers, Roy

[NMS]

Powweb has increased the cron memory therefor we can now update awstats automatically.

If you have any problems to actually make it work, you can always post here again. :)

The perfect hosting solution ;)

[RadioRob]

Hey there... as a possible idea...

Try clearing ya access log completely (download a copy for yaself first!). Set ya cron to run hourly... then have it go from there. Hopefully since it will not have to crunch so much, it will be able to update the stats for ya.

Don't know if that will work or not, but worth trying. :)

Good luck!

[njscuba]

[QUOTE]Originally posted by nmsupplies
[B]Powweb has increased the cron memory therefore we can now update awstats automatically.

Still doesn't seem to work. AWStats will only successfully update manually via cgi ( ie: click on the "update now" link in the report page )

Running it either as a cron job or manually via perl just generates "out of memory!" errors, even if you do so immediately after successfully updating by cgi.

Oh well. As long as Webalizer runs properly, AWStats is not that important, and I can live with the manual updates.

The trouble is, if you let it go too long between updates, the backlog will get bigger than memory allows, and then AWStats will cease to function until the next time you can blow away your logs.

Therefore, I would recommend that anyone who is really interested in webstats should set up Webalizer, and only use AWStats for curiosity.

[NMS]

My awstats are still updating hourly.

In fact I have now tried modify the crontab to update it daily. Do not have any trouble at all.

Did anyone manage to update awstats via crontab besides me?

[Roy]

What server are you on? Could it not be a server unique issue?

[njscuba]

good point:

venus.powweb.com

[NMS]

I am on a new server...www01

[Roy]

and I am on the infamous Comet.

Nev, perhaps you could check with your PowWeb contacts to establish if there is, in fact, a standard cronjob memory allocation on the servers.

Maybe the Starr is monitoring this thread and will contribute.

[bluesguy]

I am also on Comet and it only gives memory errors for the cron when trying to update awstats.. works fine manually once I reduced the log file to one day's worth.

[nonner]

I'm on meteor and tested the webstats script from the Webalizer cron tutorial. I used a shell program and ran the webstats command from the command line.

/usr/local/bin/webalizer -c /www/?/?????/etc/webalizer.conf -p /www/?/?????/logs/cron.log /www/?/?????/logs/cron.err

I check the etc dir and found no cron.log or err file. My webstats is not updated. It hasn't updated since I turned webstats off in ops on 1/28/03.

Shouldn't I be able to run this from a shell app?