[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] How to reduce CPU load for cron.daily tasks
- Subject: Re: [cobalt-users] How to reduce CPU load for cron.daily tasks
- From: George Kirikos <gkirikos@xxxxxxxxx>
- Date: Tue Sep 9 07:47:10 2003
- List-id: Mailing list for users to share thoughts on Sun Cobalt products. <cobalt-users.list.cobalt.com>
Hello,
--- Paul Warner <pwarner@xxxxxxxxxxxxxxxxxx> wrote:
> What can be done to reduce the load? Are there logfiles that can be
> trimmed? What are web.stats, web.cache and web.cache.new used for?
> Adding
> all items in the /home/sites/sitex/logs directory there's less than
> 10mb on
> the 'old' site.
I had the same issue on a RAQ3, and did the following after researching
the issue in Google:
1) As root, go to /usr/admserv/html/.cobalt/report and check the sizes
of mail.cache, mail.stats, web.cache, web.stats, ftp.cache, and
ftp.stats. The web.cache and and web.stats files were HUGE (like 70
MB+). I deleted all 6 files. That should remove existing summary stats
being generated in the Cobalt web GUI interface. Not a great loss, as I
never use them.
2) Edit /usr/local/sbin/split_logs (after making a backup) to comment
out the "analyze_logs", "generate_tabs" and "create_reports" function
calls, immediately after the #End SPLIT line. Doing this should mean
that the logs get split properly, but that Analog never runs. Also
should mean that the files in #1 never get generated again (and that
the .stats files in each site's individual /logs/ directory don't get
generated. Hopefully the ftp.log, web.log and mail.log continue to get
properly updated each day, though (turns out they do!)
3) Hope and pray.
It's been a few days now, and the system runs a lot smoother when it
comes to the nightly log runs. I used to get low memory errors, as the
512 MB physical RAM and the 128 MB swap were exhausted each night. But,
now only 1/2 the RAM is being used, and the swap is untouched! The logs
get split properly, too. There are residual web.sessionlog,
ftp.sessionlog and mail.sessionlog files left in the /logs/ directory,
but those get properly over-written the following night. It's almost a
*feature* to have those residual files remaining, as one can see 1-day
stats in a single file. ;)
I don't know if it'll work on a RAQ 4, but I hope something similar
works for you.
Sincerely,
George Kirikos
http://www.kirikos.com/