[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] Cobalt Raq4r log processing overloads
- Subject: Re: [cobalt-users] Cobalt Raq4r log processing overloads
- From: "Jens Kristian Søgaard" <jens@xxxxxxxxxxxxxxxxxxxx>
- Date: Sun Oct 28 06:17:01 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
Hi,
> This happens still, every morning when the logs are processed.
>Analog, Webazolver, parseReports, split_logs, etc..
> Is there anything I can do about this ? There are about 10 sites on
the
> server and average
Well, if it ain't broke, don't fix it.
The memory alert from the cobalt server is not always correct. If you
only see one a day at 04:00, and it doesn't give you any other
problems -- then just let it stay the way it is.
Apart from that, you can try:
1. Disabling analog, webalizer, split_logs, etc.
2. Try to serialize it so that split_logs, webalizer, analog, etc.
doesn't happen at the same time
3. Do logrotation more often than once a day (i.e. split the load across
the day)
--
Jens Kristian Søgaard, Mermaid Consulting I/S,
jens@xxxxxxxxxxxxxxxxxxxx,
http://www.mermaidconsulting.com/