ration Dept." <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Tuesday, December 17, 2002 5:11 PM
Subject: Re: [SAtalk] Spamd load problem
> Ok, that clears up any chance of DNS/razor backlogs, and of "old version"
> issues.
>
> Hmm, here's something to try:
>
On Tue, Dec 17, 2002 at 02:50:08PM -0500, Administration Dept. wrote:
> Hello,
>
> We are running SpamAssassin server wide via procmail and sendmail through
> /etc/procmailrc . We are having a serious load problem even using the
> spamc/spamd. The spamd processes completely hog the CPU to the po
On 2002-12-17 14:50:08 -0500, Administration Dept. wrote:
> We are running SpamAssassin server wide via procmail and sendmail through
> /etc/procmailrc . We are having a serious load problem even using the
Are you locking spamc in procmail for each mail? If not you will
get a new instance of spam
Administration Dept. wrote:
We have 512 MB of RAM, 2.5 GB Swap running Solaris 8 x86. It should be
plenty. I will try spamd on a separate server if I can't figure anything
out.
Thank you for the input.
-ed
How much free RAM do you have? I count about 26 spamd processes at about
8M residen
Ok, that clears up any chance of DNS/razor backlogs, and of "old version"
issues.
Hmm, here's something to try:
Disable the TRACKER_ID rule. There's been a recent fix to CVS that deals
with some problems with this rule causing run-away processes.
score TRACKER_ID 0
--
n Dept." <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, December 17, 2002 4:39 PM
Subject: Re: [SAtalk] Spamd load problem
> How much RAM do you have? If spamc starts swapping, you'll have a major
> thrashing problem very quickly.
>
> Use the -m parameter
Message -
From: "Matt Kettler" <[EMAIL PROTECTED]>
To: "Administration Dept." <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Tuesday, December 17, 2002 4:24 PM
Subject: Re: [SAtalk] Spamd load problem
> Hmm, There's a lot of useful info mis
How much RAM do you have? If spamc starts swapping, you'll have a major
thrashing problem very quickly.
Use the -m parameter to ensure that you don't swap, or at least don't
swap too heavily. Queuing up the messages for spam processing should
work fine during peaks (unless your system is extrem
Hmm, There's a lot of useful info missing from your question...
What version of SpamAssassin are you using? (this helps identify if it's a
known bug in an old version of SA)
Are you using razor, pyzor, or DCC?
Do you have good DNS access (ie: an on-site or on the same-server DNS server)?
How l
Hello,
We are running SpamAssassin server wide via procmail and sendmail through
/etc/procmailrc . We are having a serious load problem even using the
spamc/spamd. The spamd processes completely hog the CPU to the point
sendmail panics and reports load problems in the syslog.
Below is the load
10 matches
Mail list logo
