[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-developers] Re: Low memory warning on RaQ4
- Subject: Re: [cobalt-developers] Re: Low memory warning on RaQ4
- From: "Ian" <cobalt@xxxxxxxxxxxxx>
- Date: Fri Jan 31 04:39:01 2003
- List-id: Discussion Forum for developers on Sun Cobalt Networks products <cobalt-developers.list.cobalt.com>
On 31 Jan 2003 at 2:24, Bruce Timberlake wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> > Is there any way to get a dump of historical memory usage so I can
> > try to see what is causing the high memory drain, and what
> > processes were running at the time?
>
> Nope, you'd have to have another cron job running at the same time, or
> during that time frame, running something like "ps faux >>
> /path/to/logfile" to try and record it.
>
> I'm sure it's split_logs though, so there's not much you can do to fix
> or get rid of the problem....
If the problem is large web logs, why not try using cronolog
(http://www.cronolog.org).
This is a utility which will create daily logs straight from apache.
For example here is an extract of my httpd.conf (may wrap - should be
two lines in the vhost section):
<VirtualHost xxx.xxx.xxx.xxx>
LogFormat "%v %h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-
Agent}i\"" combined
CustomLog "|/usr/local/sbin/cronolog
/home/sites/site1/logs/%Y%m%daccess.log" combined
</VirtualHost>
This basically pipes the log data from apache to cronolog, which
looks at the name of the log file specified ( %Y%m%daccess.log ) and
replaces %Y with the year, %m with month etc.
Cronolog automatically changes the log file name at midnight -
meaning you can remove apache logs from the split_logs process.
Regards
Ian
--