Re: [SAtalk] Re: spamd dying issue

[Tomki]

Well, as I mentioned in my last email, I just kill all the zombie spamd processes every day. Depending on your server's capabilities, the hit taken by 2000 zombies by the end of the day may be a major liability, or an irritant.
For a 2.2GHz Xeon with Ultra-160 RAID5 and a Gig of RAM, it's an irritant: gets all the load averages to about 1.8.

--Tomki

At 11:00 11/19/2002 +0800, Glynn S. Condez wrote:

From: "Tomki" <[EMAIL PROTECTED]>

> Glynn,
>    From my experience, spamd occasionally dies under a fairly light
> load.  then when spamc attempts to make the connection, it barfs..  use of

from what i've seen, my 2 linux server got the same problem at the same
time.
does spamassassin connects to rbl or something similar? I don't use rbl
lookup
coz my mailscanner does, and when I kill all the process of procmail and
spamd
my mail goes out but I got mail from MailerDaemon.

how do you resolve the forked process in spamassassin 2.50cvs? If you could
give me
a solution regarding the forked process, i think its better if I upgrade my
version to 2.50cvs.
my primary mailserver process about 2000 mails everyday.

TIA
glynn


> the -f param saves the message and again, from what I've seen, the message
> is always delivered..  but the sender gets a nasty looking bounce message
> with no indication of a successful delivery.
> SpamAssassin 2.50cvs *seems* to fix that problem...  but now the issue is
> that the perl spamd processes forked off for every email processed NEVER
> DIE.   (zombies)..  so we go from easily-dying to undead.  heh
> My server currently has 1263 perl zombies because of this.  Gets to be a
> problem at around 4000, when my load maintains about 3, and the machine is
> noticably slower.  I'm just dealing with it for now because I'd rather not
> have the dying issue.  Get in in the morning, cd /etc/mail, 'make stop ;
> killall -9 perl ; make start' (I've hacked the sendmail Makefile to
> stop/start spamd)
>
> --Tomki
>
> At 10:58 11/18/2002 +0800, Glynn S. Condez wrote:
> >All,
> >
> >My spamassassin dies last November 15, 2002.
> >Im using spamassassin-2.31 and got this bunch of message in my syslog and
> >lots of procmail and spamd in the process:
> >----snip----
> >Nov 15 10:18:25 akirata spamc[13618]: connect() to spamd failed:
Connection
> >refused
> >Nov 15 10:23:47 akirata spamc[14054]: connect() to spamd failed:
Connection
> >refused
> >---snip----
> >
> >whats should be the problem? I got this the same problem with my 2 mail
> >servers both the same time.
> >
> >TIA
> >glynn
> >
> >
> >
> >
> >
> >-------------------------------------------------------
> >This sf.net email is sponsored by: To learn the basics of securing
> >your web site with SSL, click here to get a FREE TRIAL of a Thawte
> >Server Certificate: http://www.gothawte.com/rd524.html
> >_______________________________________________
> >Spamassassin-talk mailing list
> >[EMAIL PROTECTED]
> >https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
>



-------------------------------------------------------
This sf.net email is sponsored by: To learn the basics of securing
your web site with SSL, click here to get a FREE TRIAL of a Thawte
Server Certificate: http://www.gothawte.com/rd524.html
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk

-------------------------------------------------------
This sf.net email is sponsored by: To learn the basics of securing your web site with SSL, click here to get a FREE TRIAL of a Thawte Server Certificate: http://www.gothawte.com/rd524.html
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk