hi guys,


My webalizer 2.01 and the cobalt log haven't generate any log file in the past few days. What could be the problem?

<BAD THOUGHTS>
This is purely speculation, and I don't even know if this has happened before...

Perhaps someone doesn't want you to see what your server is doing. If, and that's a really big if, your server has been root-ed, the cracker might just dump your logs to /dev/null to keep you from seeing what's happening. :(

That, or your host doesn't want you to know you're over your bandwidth limit, and wants to ream you in overage charges :cool:

</END BAD THOUGHTS>

Anyway, I'd look into the programs themselves, if you have administrative access check their configuration, permissions to the directories they should be logging to, etc. Possibly restart them to see if they touch the directory, leave a trace of being started/stopped, or if they just error and politely run producing nada results.

There is only one site on the server, and I have the administrative previleage. When I loggin to the server to check the dates of the log files, they are still on
07/25/2001, something must be wrong. I restarted the server two days ago, but the log file dates still unchanged.


Could this because of the size of the log file is too big to handle?? The current size of the web.log for my site is 39MB.

BTW, a few days ago, I changed the logrotate.conf file to have the log files rotate themselves weekly, does it mean that I won't see any new stats in the colbalt log or webalizer until 5 days have passed????

File date of 'var/log/httpd/access' is 07/29/2001

file dates of all other log files in the 'log' folder of each domain is 05/25/2001

restart crond and if you got very large log files, it might be overlapping webalizer therefore webalizer wouldnt run

Could you please tell me the command for restarting the crond? Thanks.

I change the logrotate.conf to make it rotate the log files daily and it solves the problem.