You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Jai Gupta <ma...@jaigupta.com> on 2008/01/13 09:02:47 UTC
spamassassin eating lot of RAM
My server has 8GB of ram, around 4 GB is currently used by spamassassin (too
many process of /usr/bin/perl -T /usr/local/psa/admin/sbin/spammng -c -C
--max-children=1 start).
Is this normal? Can I somehow limit the process concurrency of spamassassin
or I could limit the amount of RAM it consumes?
I am tried to change max-children from 5 to 1 (by using Plesk) but no
results.
Jai
Re: spamassassin eating lot of RAM
Posted by "Daryl C. W. O'Shea" <sp...@dostech.ca>.
Jai Gupta wrote:
> My server has 8GB of ram, around 4 GB is currently used by spamassassin (too
> many process of /usr/bin/perl -T /usr/local/psa/admin/sbin/spammng -c -C
> --max-children=1 start).
"spammng" is not SpamAssassin. Tell whatever is spawning this process
to limit the number of these it spawns concurrently.
> Is this normal?
I have no idea. I don't know what "spammng" (I assume 'spam manage')
is. If it's a start up script for spamd it really should only be run
once. You only want one copy of spamd running. Perhaps a message is
passed to this process and it should really be calling spamc?
> Can I somehow limit the process concurrency of spamassassin
> or I could limit the amount of RAM it consumes?
--max-children *does* limit the number of concurrent *spamd* children.
It has nothing to do with "spammng" though.
> I am tried to change max-children from 5 to 1 (by using Plesk) but no
> results.
I'd ask some Plesk folks about "spammng" and how to control it.
Daryl
Re: spamassassin eating lot of RAM
Posted by Jai Gupta <ma...@jaigupta.com>.
Thanks Jeff,
Some stats could be seen on
http://stats.jaigupta.com/com/jaigupta.com-memory.html and
http://stats.jaigupta.com/com/jaigupta.com-processes.html
spamassassin is using RAM with an linearly increasing rate, if it is not
stopped soon my server will end with its all RAM used by spamassassin.
Do we have any other way (hacks are welcome) to minimize the resources used
by spamassassin?
I am using default rulesets that are installed with Plesk.
Jai
On Jan 13, 2008 3:02 PM, Jeff Chan <je...@surbl.org> wrote:
> In addition to setting the number of child processes to some
> reasonably small number, make sure you're not using any of the
> obsolete huge rulesets like sa-blacklist.
>
> Jeff C.
>
>
Re: spamassassin eating lot of RAM
Posted by Jeff Chan <je...@surbl.org>.
Quoting Jai Gupta <ma...@jaigupta.com>:
> My server has 8GB of ram, around 4 GB is currently used by spamassassin (too
> many process of /usr/bin/perl -T /usr/local/psa/admin/sbin/spammng -c -C
> --max-children=1 start).
>
> Is this normal? Can I somehow limit the process concurrency of spamassassin
> or I could limit the amount of RAM it consumes?
>
> I am tried to change max-children from 5 to 1 (by using Plesk) but no
> results.
In addition to setting the number of child processes to some
reasonably small number, make sure you're not using any of the
obsolete huge rulesets like sa-blacklist.
Jeff C.
Re: spamassassin eating lot of RAM
Posted by Jai Gupta <ma...@jaigupta.com>.
Thanks guys,
Problem solved now, It was a program called "watchdog" in Plesk which was
the problem. Somehow it is not detecting the status of process and is
starting the process again and again.
Jai
On Jan 14, 2008 11:38 PM, Mike Jackson <mj...@barking-dog.net> wrote:
> > My server has 8GB of ram, around 4 GB is currently used by spamassassin
> > (too many process of /usr/bin/perl -T /usr/local/psa/admin/sbin/spammng
> > -c -C --max-children=1 start).
> >
> > Is this normal? Can I somehow limit the process concurrency of
> > spamassassin or I could limit the amount of RAM it consumes?
> >
> > I am tried to change max-children from 5 to 1 (by using Plesk) but no
> > results.
>
> Plesk basically uses the system default SpamAssassin install. The
> exceptions:
>
> * It has its own startup scripts that invoke the system's spamd with its
> own options. That's spammng.
>
> * It has a replacement for spamc.
>
> * It has wrapper scripts for sa-learn.
>
> But once spamd is running, you're basically looking at a typical spamd.
> In your case, it looks like it's having problems starting up. It sounds
> like "spamassassin --lint" might be your friend here.
>
> (Oh, and different versions of SA come with Plesk. It depends on your OS
> version and version of Plesk. On Redhat, the latest version I've seen
> used is 3.1.9.)
>
Re: spamassassin eating lot of RAM
Posted by Mike Jackson <mj...@barking-dog.net>.
> My server has 8GB of ram, around 4 GB is currently used by spamassassin
> (too many process of /usr/bin/perl -T /usr/local/psa/admin/sbin/spammng
> -c -C --max-children=1 start).
>
> Is this normal? Can I somehow limit the process concurrency of
> spamassassin or I could limit the amount of RAM it consumes?
>
> I am tried to change max-children from 5 to 1 (by using Plesk) but no
> results.
Plesk basically uses the system default SpamAssassin install. The
exceptions:
* It has its own startup scripts that invoke the system's spamd with its
own options. That's spammng.
* It has a replacement for spamc.
* It has wrapper scripts for sa-learn.
But once spamd is running, you're basically looking at a typical spamd.
In your case, it looks like it's having problems starting up. It sounds
like "spamassassin --lint" might be your friend here.
(Oh, and different versions of SA come with Plesk. It depends on your OS
version and version of Plesk. On Redhat, the latest version I've seen
used is 3.1.9.)