You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Justin Mason <jm...@jmason.org> on 2004/11/24 09:38:16 UTC
Re: Weird Memory Problem
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
and try using the patch I posted recently at
http://bugzilla.spamassassin.org/show_bug.cgi?id=3983 ,
- --j.
Daniel Quinlan writes:
> "Will Kruss" <wi...@webstrikesolutions.com> writes:
>
> > We do have some custom rules from SARE and a couple of others =
> > (chickenpox/antidrug/weeds2/bogusviruswarnings).
>
> Some of these can require a lot of memory, they have not been through
> the SpamAssassin development process. Also, antidrug is included in
> SpamAssassin 3.0.0 already. Maybe you're running 2.64?
>
> Set --max-conn-per-child to a lower number of messages. That gets the
> huge processes out of the way quicker.
>
> Don't run spamc on really big messages, stick with the 250k default,
> maybe go even lower.
>
> Make sure you really need 15 children -- is that optimal for your load.
> Seems like a lot for a dual, especially if you're not using any network
> tests.
>
> Daniel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Exmh CVS
iD8DBQFBpEh4MJF5cimLx9ARArgDAJwJZI3rXOW1Hwo5mVCb7qB+FzchawCgslsO
krz6VmSWwV1XJ9gRKmMTEQI=
=dLT1
-----END PGP SIGNATURE-----
Re: Weird Memory Problem
Posted by Will Kruss <wi...@webstrikesolutions.com>.
Hi Daniel,
Interesting on the local dns issue. I am actually running spamd with the -L
option, and the local.cf is definitely being read as any changes I make
there are picked up apart from some DNS call it must be making to check
network connection every time it scans a message. I would love for someone
else to test this themselves, by modifying settings on their linux machine
to put two bogus DNS entries, then run SpamD with a -L and see what happens.
Thanks,
- Will
----- Original Message -----
From: "Daniel Quinlan" <qu...@pathname.com>
To: "Will Kruss" <wi...@webstrikesolutions.com>
Cc: "Justin Mason" <jm...@jmason.org>; <us...@spamassassin.apache.org>
Sent: Thursday, November 25, 2004 6:57 PM
Subject: Re: Weird Memory Problem
> "Will Kruss" <wi...@webstrikesolutions.com> writes:
>
>> I have written a script which simply monitors the spamd processes and if
>> one
>> increases above 200mb virtual it gets killed, if that fails I'll look to
>> implementing your suggestion Justin.
>
> The patch Justin mentioned should help. Please try that before your
> script. :-)
>
>> Does the dns_available tag still function in version 3.0.1 of spamd?
>
> It should, if it doesn't, your local.cf might not be getting read (best
> guess). You can also run "spamd -L" to only run local tests.
>
> Daniel
>
> --
> Daniel Quinlan
> http://www.pathname.com/~quinlan/
Re: Weird Memory Problem
Posted by Daniel Quinlan <qu...@pathname.com>.
"Will Kruss" <wi...@webstrikesolutions.com> writes:
> I have written a script which simply monitors the spamd processes and if one
> increases above 200mb virtual it gets killed, if that fails I'll look to
> implementing your suggestion Justin.
The patch Justin mentioned should help. Please try that before your
script. :-)
> Does the dns_available tag still function in version 3.0.1 of spamd?
It should, if it doesn't, your local.cf might not be getting read (best
guess). You can also run "spamd -L" to only run local tests.
Daniel
--
Daniel Quinlan
http://www.pathname.com/~quinlan/
Re: Weird Memory Problem
Posted by Will Kruss <wi...@webstrikesolutions.com>.
Thanks Guys,
I'm definitely running 3.0.1 and have removed the custom rulesets that are
included in SpamAssassin3. The problem isn't with the rulesets though as I
was running SpamD2.64 prior with the same rulesets and had no issues.
I have written a script which simply monitors the spamd processes and if one
increases above 200mb virtual it gets killed, if that fails I'll look to
implementing your suggestion Justin.
I do have one further question however. I eventually figured out why I was
having so many issues, the boxes didn't have fast DNS servers setup on them,
and even though i have specified
dns_available no
in the local.cf file, it still was taking about 30 seconds to respond to a
query. I setup an internal DNS server in the network config for the server,
and all of a sudden it processes the same messages in 0.0 or 0.1 seconds.
Does the dns_available tag still function in version 3.0.1 of spamd?
Thanks guys,
- Will
----- Original Message -----
From: "Justin Mason" <jm...@jmason.org>
To: "Daniel Quinlan" <qu...@pathname.com>
Cc: "Will Kruss" <wi...@webstrikesolutions.com>;
<us...@spamassassin.apache.org>
Sent: Wednesday, November 24, 2004 7:38 PM
Subject: Re: Weird Memory Problem
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> and try using the patch I posted recently at
> http://bugzilla.spamassassin.org/show_bug.cgi?id=3983 ,
>
> - --j.
>
> Daniel Quinlan writes:
>> "Will Kruss" <wi...@webstrikesolutions.com> writes:
>>
>> > We do have some custom rules from SARE and a couple of others =
>> > (chickenpox/antidrug/weeds2/bogusviruswarnings).
>>
>> Some of these can require a lot of memory, they have not been through
>> the SpamAssassin development process. Also, antidrug is included in
>> SpamAssassin 3.0.0 already. Maybe you're running 2.64?
>>
>> Set --max-conn-per-child to a lower number of messages. That gets the
>> huge processes out of the way quicker.
>>
>> Don't run spamc on really big messages, stick with the 250k default,
>> maybe go even lower.
>>
>> Make sure you really need 15 children -- is that optimal for your load.
>> Seems like a lot for a dual, especially if you're not using any network
>> tests.
>>
>> Daniel
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (GNU/Linux)
> Comment: Exmh CVS
>
> iD8DBQFBpEh4MJF5cimLx9ARArgDAJwJZI3rXOW1Hwo5mVCb7qB+FzchawCgslsO
> krz6VmSWwV1XJ9gRKmMTEQI=
> =dLT1
> -----END PGP SIGNATURE-----
>