[cobalt-users] Webalizer and large logs

[Jeff Lasman <jblists@xxxxxxxxxxxxx>]

We've been trying to figure out why webalizer seems to occasionally (but
definitely on a pattern) lose data.  One one site it's been happening
every other day; on another every four days.

I think I've finally traced it to the interaction between logrotate,
split_logs and when webalizer runs.

Webalizer, whether installed by Cobalt Professional Services (one of our
systems was installed by them), or from a package, by default runs after
logrotate.

Logrotate first splits logs, then passes control to the logrotate
configuration on a per-site basis.  The logrotate configuration zips up
the logs depending on how big they get.

That happens BEFORE webalizer runs.  And it appears as if webalizer is
NOT set up to read zipped files.

Someone once posted to solve the problem by running webalizer before
logrotate, but under best-case scenario that delays logs from appearing
for an extra day, and in worst-case scenario doesn't help; log info
still vanishes.

We're looking at configuring webalizer to read zipped files, since
setting a size for logrotation, to make sure the data is where it's
supposed to be for at least one run of webalizer appears to be a
hit-and-miss proposition.

Anyone else run into these issues?

If so, what did you do to solve them?

Thanks.

Jeff
-- 
Jeff Lasman, nobaloney.net, P. O. Box 52672, Riverside, CA  92517 US
Internet & Unix/Linux/Sun/Cobalt Consulting +1 909 778-9980
Our jblists address used on lists is for list email only
To contact us offlist: "http://www.nobaloney.net/contactus.html";