Re: RE : RE : [cobalt-users] Strange Memory problem

[Bruce Timberlake <bruce@xxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sat December 14 2002 23:05, Jean-Françoys Auclair wrote:
> Only since 2 week..
>
> Posgres stop..
> Memory load high.. 95-97%
> CPU load high.. 95-97%
>
> It's the reason why I've had more RAM.. (+512) this Friday.. No
> succes.. Same problem this morning
>
> I think I have a problem with logrotation but I'm not sure..

Yeah, if you're getting Active Monitor alerts, that's a problem.

And yes, the logrotate process, especially parseReport.pl, can be a 
big RAM hog, especially around 4am when the whole process kicks off. 
What time of day are you getting the AM reports (or is it somewhat 
continuous)?

If you have huge logfiles (check out /var/log/httpd/access, as that's 
the biggy that parseReport tries to chop up and hand out to each 
site, before calculating each site's usage), and the server is busy 
enough to keep parseReport from happening as it's supposed to, that 
could be dragging the box down.

If you shell into the server, and run top, you can sort the processes 
by resident RAM used ("M") or CPU utilization ("P")...  this might 
give you some insight into what's going on...?

- -- 
Bruce Timberlake

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE9/CvxvLA2hUZ9kgwRAgU+AJ9p/ZrRGLa27dS+ePQKUmO3IIHJkgCfWqcV
BqOUVyRnegQC70ygWBbCYZ8=
=pmHR
-----END PGP SIGNATURE-----