[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] RAQ4 slowing down with high processor load.
- Subject: Re: [cobalt-users] RAQ4 slowing down with high processor load.
- From: Lauchlin <lauchlin_list@xxxxxxxxxxxx>
- Date: Wed Feb 4 16:58:01 2004
- List-id: Mailing list for users to share thoughts on Sun Cobalt products. <cobalt-users.list.cobalt.com>
On 05/02/2004, at 3:50 AM, Neil James wrote:
On 4 Feb 2004 at 8:11, Lauchlin wrote:
Ok to fix this you need to modify system files so only do it if you
know you can fix anything that breaks. Remember it is a good idea to
make copies of any files you modify so you can just copy them back in
later if all hell breaks loose.
Ooer - that's me sweating already then :) I only learned about top
last weekend which let me find
out what the problem was in the first place. I'll make sure I have my
trusty copy of 'Linux
sysadmin unleashed' to hand.
This hack will totaly kill the statistics in the admin area of the
cobalt...but who cares...they are crap anyway.
Is this the one that gives the dodgy graphics of how much bandwidth
each service/domain has
used? I can live without that - in any case I have webalizer
installed for access stats.
Yes. I hate those stats..they mean nothing.
The brute force way to stop this is to stop analog (which is called
from split_logs, which is in turn called from the apache stanza of the
logrotate, which is in turn called from CRON) from running as that is
what is taking up all the CPU cycles..
Would it be easier to delete the existing log files?
Webalizer uses these logs to generate it's stats as well I think so
deleting them will probably kill webalizer. I guess another way to do
it would be to create a script that deletes the previous days logs or
something.
so
you could chuck a script called 01killyesterdayslogs in
/etc/cron.daily/ which just has the following lines:
#!/bin/bash
for a in `/bin/ls -1F /home/sites/ |grep "/"`; do rm
/home/sites/$a/logs/*; done
That will nuke eveything in each sites log directory before it does the
days log splitting and rotating...or I guess you could throw it in cron
monthly or something.
Then you could possibly comment out lines 3-6 in /etc/logrote.d/proftpd
and lines 26-29 in /etc/logrotate.d/syslog That will stop logrotate
splitting the ftp and e-mail logs...which you probably don't care about
anyway.
That way it will only rotate and split the logs you want. Then you'd
probably find that it would run fine with the RAM you already have.
I don't mind losing the access data. Perhaps
then the whole thing would run OK in the RAM we have? After all, it's
been running OK up to
now. If so - then exactly which log files are we talking about?
I really appreciate your help with this - thanks very much for your
time.
Neil
No problems...gave me some ideas too. Hope those few ideas set you on
the right path. Once you start looking there is an amazing amount of
crap on the RaQ4s that you can strip out and optimize while still
retaining the easy to use web interface.
--
Lauchlin Wilkinson, BComp
Technical Manager
Internet Tasmania Pty. Ltd.