Re: [cobalt-users] Webalizer - logrotate - missing days

[Edwin Groenescheij <edwin@xxxxxxxxxxxxxxxx>]

Mark Thompson - Mailing Lists wrote:
> 
> For a long time I've notice that sites are missing days but now I have a
> larger site that never gets processed.  I've narrowed this down to the
> logfile being rotated away before Webalizer gets ahold of it.  I could just
> make the threshold for logrotate a lot higher but it would still get
> rotated away every so often.
> 
> Has anyone found a good solution for this?  I've searched the archives here
> and found someone who suggested manually doing this for sites that I care
> to know about.
> 
> It seems like the problem is that Webalizer and logrotate are run in the
> same daily cron cycle simultaneously at 4:02 am.  I would just run
> logrotate an hour later but I'm not sure whether logrotate needs to be run
> to split the logfiles first.
> 
> Could someone tell me whether logrotate does this original splitting or is
> it just responsible for the rotating and compressing of the logfiles after
> they've been split?

You could change the daily cron's for splitting/rotating the
logs, but this might void Cobalt's warranty or might be
overwritten by one of the next Cobalt jumbo patches. 

I wrote a script which creates the webalizer stats daily (a bit
later than the logrotation stuff). My script checks if the log
file exists, is empty, is rotated etc. If it just has been
rotated the script first uses the compressed log for the
webalizer stats and then the new one.

If you would like some help with creating a script like this
contact me direct by e-mail.

Cheers,
Edwin