Re: spamd dies - please help - SOLVED
Back on-list, just FYI.
On Sun, 2009-06-07 at 22:41 -0300, Soporte Técnico elbolson.com wrote:
Thanks for your answer.
It is solved now - I removed a plugin that a friend created to call KAV
antivirus, based on Clamav plugin. It had worked before on i386, it
doesn't work on x86_64. We will investigate why. Clamav plugin works
allright.
Greetings
Claudia Burman
El Bolson - Patagonia Argentina
Useless full-quote snipped.
--
char *t=\10pse\0r\0dtu...@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4;
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;il;i++){ i%8? c=1:
(c=*++x); c128 (s+=h); if (!(h=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
Re: spamd dies - please help
On Sat, 2009-06-06 at 19:34 -0300, Claudia Burman wrote:
This is the problem:
When I send a mail everything works, ps ax shows spamd and two childs.
Sending a big load of mails, I begin to see spamd defunct processes.
Please elaborate on that.
After a while (and after some messages are correctly delivered), I see
this in the log
Jun 6 13:36:58 mail spamd[13000]: prefork: cannot ping 14503, file handle
not defined, child likely to still be processing SIGCHLD handler after
killing itself
Jun 6 13:36:58 mail spamd[13000]: prefork: killed child 14503
(one for each process)
How many spamd child processes are that at this point? What do the log
lines like prefork: child states read?
Any chance the load of the system at that time is extremely high? Do you
hit swap?
and after that
connect to spamd on 127.0.0.1 failed, retrying (#3 of 3): Connection refused
the message is delivered but is not passed through spamassassin.
Yes, that's cause there are no reachable spamds, and spamc is being run
with the default safe fallback. So it continues with the unprocessed
message in case of problems.
--
char *t=\10pse\0r\0dtu...@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4;
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;il;i++){ i%8? c=1:
(c=*++x); c128 (s+=h); if (!(h=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
spamd dies - please help
Hi,
I am trying to setup a new mail server. With postfix - dovecot ldap -
spamd. All virtual users. Over Centos 5.3 64 bits. Spamassassin version is
3.2.5 installed with yum.
This is the line in postfix's master.cf
dovecot unix - n n - 30 pipe
flags=DRhu user=vmail argv=/usr/bin/spamc -s 204800 -u $user -e
/usr/libexec/dovecot/deliver -d ${user}
This is how spamd is started
-d -l -x -m 35 -u vmail
--virtual-config-dir=/var/spool/postfix/virtual/%u/spamassassin
This is the problem:
When I send a mail everything works, ps ax shows spamd and two childs.
Sending a big load of mails, I begin to see spamd defunct processes.
After a while (and after some messages are correctly delivered), I see
this in the log
Jun 6 13:36:58 mail spamd[13000]: prefork: cannot ping 14503, file handle
not defined, child likely to still be processing SIGCHLD handler after
killing itself
Jun 6 13:36:58 mail spamd[13000]: prefork: killing failed child 14503
fd=undefined at
/usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/SpamdForkScaling.pm
line 171, DATA line 275.
Jun 6 13:36:58 mail spamd[13000]: prefork: killed child 14503
(one for each process)
and after that
connect to spamd on 127.0.0.1 failed, retrying (#3 of 3): Connection refused
the message is delivered but is not passed through spamassassin.
Any help will be appreciated. I can provide aditional info if necessary.
Thanks
Claudia Burman
El Bolson - Patagonia Argentina
spamd dies for no apparent reason
Having an issue with spamd terminating abnormally. The server is
running FreeBSD 6.0-Release, Perl 5.8.8, and SA 3.1.5.
spamd is started with the following:
-d -r ${pidfile} -m 15 -i 127.0.0.1 -p 783 -s /var/log/spamd.log
The ${pidfile} is set from within /usr/local/etc/rc.d/sa-spamd.
I've checked through the spamd.log file created and can not find
anything to indicate why this is happening.
I've also made sure 'spamassassin --lint' comes out clean.
I do use sa-update and had to remove the rules that I loaded into
/usr/local/etc/mail/spamassassin as they were causing a conflict.
That conflict wasn't visible until after I started logging.
If there is something I'm missing, please point out what. Thanks.
--
This message was sent using 100% recycled electrons.
RE: spamd dies for no apparent reason
I was having similar problems and I finally setup a rule to limit
message sizes that were sent to SA which seems to have resolved it.
Perhaps it's some sort of spammer DoS?
--
Benjamin Story, CCNA CCDA CQS-CFWS
Network Administrator
Dot Foods, Inc
www.dotfoods.com
IT Helpdesk x2312 or [EMAIL PROTECTED]
-Original Message-
From: Duane Hill [mailto:[EMAIL PROTECTED]
Sent: Friday, September 15, 2006 9:20 AM
To: users@spamassassin.apache.org
Subject: spamd dies for no apparent reason
Having an issue with spamd terminating abnormally. The server is
running FreeBSD 6.0-Release, Perl 5.8.8, and SA 3.1.5.
spamd is started with the following:
-d -r ${pidfile} -m 15 -i 127.0.0.1 -p 783 -s /var/log/spamd.log
The ${pidfile} is set from within /usr/local/etc/rc.d/sa-spamd.
I've checked through the spamd.log file created and can not find
anything to indicate why this is happening.
I've also made sure 'spamassassin --lint' comes out clean.
I do use sa-update and had to remove the rules that I loaded into
/usr/local/etc/mail/spamassassin as they were causing a conflict.
That conflict wasn't visible until after I started logging.
If there is something I'm missing, please point out what. Thanks.
--
This message was sent using 100% recycled electrons.
Re: spamd dies for no apparent reason
Duane Hill wrote:
Having an issue with spamd terminating abnormally. The server is
running FreeBSD 6.0-Release, Perl 5.8.8, and SA 3.1.5.
All the spamd processes actually terminate? Not end up like zombies or
stop responding?
spamd is started with the following:
-d -r ${pidfile} -m 15 -i 127.0.0.1 -p 783 -s /var/log/spamd.log
The ${pidfile} is set from within /usr/local/etc/rc.d/sa-spamd.
I've checked through the spamd.log file created and can not find
anything to indicate why this is happening.
I've also made sure 'spamassassin --lint' comes out clean.
I do use sa-update and had to remove the rules that I loaded into
/usr/local/etc/mail/spamassassin as they were causing a conflict.
That conflict wasn't visible until after I started logging.
What kind of conflict are you talking about here?
If there is something I'm missing, please point out what. Thanks.
After how many messages does spamd exhibit the problem? How many
children are running? Are you using pre-forking or round-robin?
Does-rescanning the last message processed by each child, or at least
the very last message to be scanned, cause the problem to happen again
(after you've restarted spamd, of course).
Daryl
Re: spamd dies for no apparent reason
On Friday, September 15, 2006 at 6:36:01 PM, Daryl confabulated:
Duane Hill wrote:
Having an issue with spamd terminating abnormally. The server is
running FreeBSD 6.0-Release, Perl 5.8.8, and SA 3.1.5.
All the spamd processes actually terminate? Not end up like zombies or
stop responding?
I do not believe so. Viewing processes with 'ps' and grep'ing for
spamd yields nothing. Normally it shows something like this:
[EMAIL PROTECTED] ~]$ ps auxw | grep spamd
nobody 6899 18.6 5.5 57400 56716 ?? S 6:43PM 1:31.52 spamd child
(perl5.8.8)
nobody 7343 15.3 5.2 54220 53628 ?? S 6:51PM 0:15.46 spamd child
(perl5.8.8)
root 87623 0.0 4.7 49420 48852 ?? Ss2:12PM 2:56.78
/usr/local/bin/spamd -m 15 -i 127.0.0.1 -p 783 -u nobody -g nobody -
After spamd is no longer active, there isn't anything displayed for
the process.
I did forget to mention I was running spamd under the nobody
user/group. However, I was having this same issue running without the
-u and -g start parameters.
spamd is started with the following:
-d -r ${pidfile} -m 15 -i 127.0.0.1 -p 783 -s /var/log/spamd.log
The ${pidfile} is set from within /usr/local/etc/rc.d/sa-spamd.
I've checked through the spamd.log file created and can not find
anything to indicate why this is happening.
I've also made sure 'spamassassin --lint' comes out clean.
I do use sa-update and had to remove the rules that I loaded into
/usr/local/etc/mail/spamassassin as they were causing a conflict.
That conflict wasn't visible until after I started logging.
What kind of conflict are you talking about here?
If there is something I'm missing, please point out what. Thanks.
After how many messages does spamd exhibit the problem? How many
children are running? Are you using pre-forking or round-robin?
Does-rescanning the last message processed by each child, or at least
the very last message to be scanned, cause the problem to happen again
(after you've restarted spamd, of course).
Daryl
--
This message was sent using 100% recycled electrons.
3.1.2 spamd dies without warning
I upgraded from 3.0.4 yesterday without too much trouble...once I got 3.1.2 online, I noticed a nice reduction in false negatives, and cpu remained low (holiday here in US). This morning, spamd died with no warning, except of course a huge increase in spam. Nothing in /var/log/messages, and only this in maillog: May 30 08:19:27 mail spamd[83175]: spamd: result: Y 44 - BAYES_99,EXTRA_MPART_TY PE,HELO_DYNAMIC_HCC,HELO_DYNAMIC_IPADDR2,HTML_90_100,HTML_IMAGE_ONLY_08,HTML_MES SAGE,HTML_SHORT_LINK_IMG_1,INFO_TLD,MIME_HTML_MOSTLY,RAZOR2_CF_RANGE_51_100,RAZO R2_CF_RANGE_E4_51_100,RAZOR2_CHECK,RCVD_IN_NJABL_DUL,URIBL_JP_SURBL,URIBL_OB_SUR BL,URIBL_SC_SURBL,URIBL_WS_SURBL scantime=1.5,size=13627,user=simscan,uid=0,requ ired_score=6.0,rhost=localhost.pil.net,raddr=127.0.0.1,rport=2895,mid=000c01c68 [EMAIL PROTECTED],bayes=0.9998609,autolearn=spam May 30 08:19:34 mail spamc[83329]: connect(AF_INET) to spamd at 127.0.0.1 failed, retrying (#1 of 3): Connection refused May 30 08:19:34 mail spamc[83359]: connect(AF_INET) to spamd at 127.0.0.1 failed, retrying (#1 of 3): Connection refused It took me about an hour and a half to notice it. I restarted spamd and it's going ok at moderate cpu use. Here are my flags with which I start spamd: /usr/local/bin/spamd -m 15 -d -x -r /var/run/spamd.pid The only changes I made with the upgrade were that I enabled SPF, DCC and Pyzor. When building the new version, it did complain about an outdated razor2 software, but as it was only a warning (and I'd never had problems with it before), I didn't bother to UG. Any ideas as to the possible cause? James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am =
Re: 3.1.2 spamd dies without warning
On Tue, May 30, 2006 at 10:31:27AM -0400, [EMAIL PROTECTED] wrote: BTW, can anybody tell me whether or not spamd re-reads the .pre files if you just give it a SIG HUP, or do you have to kill and restart it (I did that this time anyway)? A HUP should cause spamd to re-exec (basically killing itself off and restarting), reading in all the config files again. -- Randomly Generated Tagline: You have to stay in shape. My grandmother, she started walking 5 miles a day when she was 60. She's 97 today and we don't know where the hell she is. - Ellen DeGeneres pgpQfs7H8PzLN.pgp Description: PGP signature
Re: spamd dies with
On Thu, 29 Sep 2005, A J Thew wrote: From: A J Thew [EMAIL PROTECTED] To: users@spamassassin.apache.org Date: Thu, 29 Sep 2005 11:33:42 +0100 Subject: spamd dies with It appears that this (or similar) has been see by others but I'll give my 2p worth http://bugzilla.spamassassin.org/show_bug.cgi?id=4594 ... at this point spamd stops responding complely until shutdiwn and re-started. I've reverted to --round-robin It'll be cold comfort to you, but note that this doesn't affect everyone. I've been happily using the Apache httpd server model of hot child processes for spamd since Justin Mason produced the patch for SpamAssassin-3.0.1. Currently running with that patch applied to SpamAssassin-3.0.4 and I don't anticipate any problems with SpamAssassin-3.1.0. Especially as I've got SpamAssassin-3.1.0 running on a dual-procesor OpenBSD box OK. My production machines are single-processor OpenBSD boxes. The last time I restarted spamd on the production boxes was 4th July[1]. So they've been running happily for nearly three months. The permanent spamds managing the child processes have all clocked up 26 or 27 minutes of CPU time. Seems a bit pointless that I'm runnning spamd under the control of daemontools to ensure it does keep running. [1] Yes this does mean I'm running with some slightly outdated rules from the SpamAssassin Rules Emporium. The rules have been updated, I just need to restart spamd to pick them up. Seems such a shame when it's been performing so well :-) -- Dennis Davis, BUCS, University of Bath, Bath, BA2 7AY, UK [EMAIL PROTECTED] Phone: +44 1225 386101
spamd dies with
It appears that this (or similar) has been see by others but I'll give my 2p worth http://bugzilla.spamassassin.org/show_bug.cgi?id=4594 Sep 28 20:16:53 mx1 spamd[25801]: prefork: syswrite(9) failed, retrying... at /usr/lib/perl5/site_perl/5.6.1/Mail/SpamAssassin/SpamdForkScaling.pm line 554. Sep 28 20:16:58 mx1 spamd[25801]: prefork: syswrite(9) failed, retrying... at /usr/lib/perl5/site_perl/5.6.1/Mail/SpamAssassin/SpamdForkScaling.pm line 554. and later Sep 28 20:21:54 mx1 spamd[22685]: prefork: sysread(10) failed after 300 secs at /usr/lib/perl5/site_perl/5.6.1/Mail/SpamAssassin/SpamdForkScaling.pm line 501. Sep 28 20:21:54 mx1 spamd[24252]: prefork: sysread(11) failed after 300 secs at /usr/lib/perl5/site_perl/5.6.1/Mail/SpamAssassin/SpamdForkScaling.pm line 501. Sep 28 20:21:54 mx1 spamd[22395]: prefork: sysread(11) failed after 300 secs at /usr/lib/perl5/site_perl/5.6.1/Mail/SpamAssassin/SpamdForkScaling.pm line 501. and then Sep 28 20:22:00 mx1 spamd[25801]: spamd: handled cleanup of child pid 19646 due to SIGCHLD Sep 28 20:22:00 mx1 spamd[25801]: prefork: syswrite(9) failed, retrying... at /usr/lib/perl5/site_perl/5.6.1/Mail/SpamAssassin/SpamdForkScaling.pm line 554. at this point spamd stops responding complely until shutdiwn and re-started. I've reverted to --round-robin Alan Thew
RE: Spamd dies after tcp timeout
I did some more digging, and I also find the following entry several times in the maillog: prefork: select returned undef! recovering Spamd is currentlty die-ing twice a day :-| Never had any problem with any other version in this regard... Kind Regards, Sander Holthaus - Orange XL From: Sander Holthaus - Orange XL [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 27, 2005 9:21 PM To: users@spamassassin.apache.org Subject: Spamd dies after tcp timeout Since a few days, I been having more serious problems with SpamAssassin 3.10. It just dies after the following two messages in the error-log: Sep 27 15:16:32 OrangeXL4 spamd[63730]: prefork: child states: II Sep 27 15:18:12 OrangeXL4 spamd[63730]: tcp timeout at /usr/local/lib/perl5/site_perl/5.8.5/Mail/SpamAssassin/SpamdForkScaling.pm line 195. Sep 27 15:18:12 OrangeXL4 spamd[63730]: tcp timeout at /usr/local/lib/perl5/site_perl/5.8.5/Mail/SpamAssassin/SpamdForkScaling.pm line 195. Next to that, I get quite a few Pyzor / Alarm erros (for about 5% of all mail). Never had any of such problems with SpamAssassin 3.0.x or 2.xx I'm using SpamAssassin on FreeBSD 4.10 with Perl 5.8.5 installed. Kind Regards, Sander Holthaus
Spamd dies after tcp timeout
Since a few days, I been having more serious problems with SpamAssassin 3.10. It just dies after the following two messages in the error-log: Sep 27 15:16:32 OrangeXL4 spamd[63730]: prefork: child states: IISep 27 15:18:12 OrangeXL4 spamd[63730]: tcp timeout at /usr/local/lib/perl5/site_perl/5.8.5/Mail/SpamAssassin/SpamdForkScaling.pm line 195.Sep 27 15:18:12 OrangeXL4 spamd[63730]: tcp timeout at /usr/local/lib/perl5/site_perl/5.8.5/Mail/SpamAssassin/SpamdForkScaling.pm line 195. Next to that, I get quite a few Pyzor / Alarm erros (for about 5% of all mail). Never had any of such problems with SpamAssassin 3.0.x or 2.xx I'm using SpamAssassin on FreeBSD 4.10 with Perl 5.8.5 installed. Kind Regards, Sander Holthaus
Re: Spamd dies after tcp timeout
Sander Holthaus - Orange XL wrote: Next to that, I get quite a few Pyzor / Alarm erros (for about 5% of all mail). Never had any of such problems with SpamAssassin 3.0.x or 2.xx The error has actually always been present. We just didn't report it before. If you were to call Pyzor independently you'd see the same error just as often. There's a third party patch for Pyzor available: Patches (you need all three): http://antispam.imp.ch/08-opensource.html?lng=0 Discussion: http://bugzilla.spamassassin.org/show_bug.cgi?id=4580 Daryl
RE: SPAMD dies
I run into this as well, sometimes it will run along great, and then just out of the blue die with no reason or errors that I can find. Actually happened to me this morning, woke up to a pile of spam in my mailbox, and thought guess spamd died off, time to restart it. I have it running on FreeBSD 4.x and 5.x servers, and now actually 6.x servers, and all of them seem to do this from time to time, and have with any of the SA3.x releases up to the most current 3.0.4 version. FYI, I use procmail to invoke spamc and process via spamd, as sendmail uses procmail as my delivery agent. So though I don't have a solution, your sure not the only one that sees this happen.. :) --- Howard Leadmon -Original Message- From: Daryl C. W. O'Shea [mailto:[EMAIL PROTECTED] Sent: Friday, July 15, 2005 2:03 AM To: Thomas Kinghorn [MTNNS -Rosebank] Cc: users@spamassassin.apache.org Subject: Re: SPAMD dies Thomas Kinghorn [MTNNS -Rosebank] wrote: Good morning list. I am having issues with SPAMD just dying and no info being shown in the logs to help troubleshoot. The system is running Redhat 9, Latest versions of Exim spamassassin. Spamassassin uses pyzor, razor dcc. What latest version of SpamAssassin are you using? Have you (or a distribution maintainer) applied any patches to it? Daryl
RE: SPAMD dies
I run into this as well, sometimes it will run along great, and then just out of the blue die with no reason or errors that I can find. Actually happened to me this morning, woke up to a pile of spam in my mailbox, and thought guess spamd died off, time to restart it. My SpamD didn't die literally, but would stop functioning, just seeming to hang when asked to classify spam. I am running on Cygwin and put it down to the OS-environment, but on testing the cvs snapshots (3.10pre4+) my initial, very brief evaluation (and hope) is that the problem is reduced (or eliminated.) -- Herb Martin
Re: SPAMD dies
Thomas Kinghorn [MTNNS -Rosebank] wrote: Good morning list. I am having issues with SPAMD just dying and no info being shown in the logs to help troubleshoot. The system is running Redhat 9, Latest versions of Exim spamassassin. Spamassassin uses pyzor, razor dcc. What latest version of SpamAssassin are you using? Have you (or a distribution maintainer) applied any patches to it? Daryl
RE: SPAMD dies
Daryl C. W. O'Shea wrote: Thomas Kinghorn [MTNNS -Rosebank] wrote: Good morning list. I am having issues with SPAMD just dying and no info being shown in the logs to help troubleshoot. The system is running Redhat 9, Latest versions of Exim spamassassin. Spamassassin uses pyzor, razor dcc. What latest version of SpamAssassin are you using? Have you (or a distribution maintainer) applied any patches to it? Daryl Apologies. I am running Spamassassin 3.0.4 (latest stable release) and The only patch I have used is the sa-exim patch. Regards Tom
SPAMD dies
Title: SPAMD dies Good morning list. I am having issues with SPAMD just dying and no info being shown in the logs to help troubleshoot. This is what I have: Jul 15 01:01:04 jp-mx-1 spamd[16441]: identified spam (8.8/4.4) for xadmin:501 in 4.5 seconds, 5865 bytes.Jul 15 01:01:04 jp-mx-1 spamd[16441]: result: Y 8 - AWL,BAYES_99,J_CHICKENPOX_31,J_CHICKENPOX_41,J_CHICKENPOX_47,NO_REAL_NAME,PYZOR_CHECK scantime=4.5,size=5865,mid=[EMAIL PROTECTED],bayes=1,autolearn=no Jul 15 01:03:11 jp-mx-1 spamc[17673]: connect(AF_INET) to spamd at 127.0.0.1 failed, retrying (#1 of 3): Connection refused Jul 15 01:03:12 jp-mx-1 spamc[17673]: connect(AF_INET) to spamd at 127.0.0.1 failed, retrying (#2 of 3): Connection refusedJul 15 01:03:13 jp-mx-1 spamc[17673]: connect(AF_INET) to spamd at 127.0.0.1 failed, retrying (#3 of 3): Connection refused Jul 15 01:03:14 jp-mx-1 spamc[17673]: connection attempt to spamd aborted after 3 retries The system is running Redhat 9, Latest versions of Exim spamassassin. Spamassassin uses pyzor, razor dcc. Many thanks Tom
