[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] remove spamassassin spamd
- Subject: Re: [cobalt-users] remove spamassassin spamd
- From: Greg Hewitt-Long <cobaltusers@xxxxxxxxxxxxxxxxxxx>
- Date: Thu Feb 5 07:26:02 2004
- List-id: Mailing list for users to share thoughts on Sun Cobalt products. <cobalt-users.list.cobalt.com>
At 07:26 AM 2/5/2004, you wrote:
Hello,
I am having problems with my Raq4 crashing quite regularly at around 4.00am
during/after logs are being rotated. Also getting CPU load high, memory low
and SMTP server broken messages.
Quite simply there is not enough resources for my Raq4 with 128 ram to
handle all these processes. The problem started shortly after U installed
Spamassassin. Although I not blaming Spamassassin for the problem, I think
that the extra load on the server with this software installed was the
"straw that broke the camels back".
Your raq would have been struggling with so little RAM a long time
back. Put simply, 128Mb of RAM is not adequate for anything but a few
sites being virtually hosted. Add any software (mailscanner, spamassassin,
anti-virus, webalizer) and you would have problems. Even with a large
site, the log rotation would have cause the RAQ to page with so little RAM.
Add more RAM.
Earlier this week I removed MailScanner to see if this would help, but
server crashed again this morning and I had to request a reboot. Today I
tried to remove the Spamassassin Pkg, but received an message during
uninstall stating that it could not remove spamd. When I run 'top' spamd is
still running. How can I remove this?
It's not spamd alone. I'd hazard a guess that one of your sites has hit a
plateau and is locking up during rotation.
cd /etc/logrotate.d
grep -i size *
If you have large numbers in there, partularly anything 50M or higher,
you're going to to feel pain during logrotation.
You can MANUALLY edit these files and reduce the size of the logs before
they rotate, they are defaulted to 10% of the virtual host's available
space - which for email and ftp logs can be really high - and we have a
couple of sites with 1000Mb or 1500Mb - these do not need to have 100Mb or
150Mb logfiles, so web was reduced to 50Mb each and email and ftp to 15Mb
each site - this is more than adequate for these site (most sites).
I'm still not sure if this will sort out the bigger problem of the server
crashing, but I'm just trying to eliminate the possibilities.
Add more RAM, and reduce the load on the log rotation script - you might
need to "manually" blow away any really large logfiles
cp /dev/null LOGFILE
hth
Greg
Thanks,
Declan.
_____________________________________
cobalt-users mailing list
cobalt-users@xxxxxxxxxxxxxxx
To subscribe/unsubscribe, or to SEARCH THE ARCHIVES, go to:
http://list.cobalt.com/mailman/listinfo/cobalt-users