Bug 2961 - spamd receives SIGPIPE after long processing time
Summary: spamd receives SIGPIPE after long processing time
Status: RESOLVED WONTFIX
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: spamc/spamd (show other bugs)
Version: 2.63
Hardware: PC Linux
: P4 normal
Target Milestone: Undefined
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-24 07:38 UTC by J C Schulz
Modified: 2005-01-21 02:18 UTC (History)
0 users


Attachment Type Modified Status Actions Submitter/CLA Status
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description J C Schulz 2004-01-24 07:38:50 UTC 
I'm occasionally seeing this in my log from spamd:

Jan 24 00:17:55 xxxx spamd[21298]: identified spam (35.2/4.5) for xxx:??? in
723.6 seconds, 1990 bytes.
Jan 24 00:17:55 xxxx spamd[21298]: identified spam (35.2/4.5) for xxx:??? in
723.6 seconds, 1990 bytes.
Jan 24 00:17:55 xxxx spamd[21298]: SIGPIPE received - reopening log socket

I increased the TIMEOUT parameter in my procmailrc to 1536 seconds thinking
procmail might be killing spamc after the default timeout period of 960 seconds.
I'm using perl v5.8.1. Any additional debugging I can turn on to try and track
down the source of the SIGPIPE?
Comment 1 Theo Van Dinter 2004-02-27 00:08:46 UTC 
I'm less worried about SIGPIPE and more worried why it's taking you 730+ seconds to scan a single 
message.  Perhaps you have DCC or pyzor enabled?  Try disabling them and see what happens.
Comment 2 Nikos Karamanolis 2004-09-16 01:10:07 UTC 
The same here. On a Sun Solaris system with 256Mb RAM running ONLY spamassassin
and clamav deamons. Some of the logs:

----------- syslog --------------

Sep 16 09:45:33 dolphin.dea.gr spamd[22183]: identified spam (9.0/5.0) for clama
v:1180 in 197.0 seconds, 18748 bytes.
Sep 16 09:45:33 dolphin.dea.gr spamd[22184]: identified spam (7.5/5.0) for clama
v:1180 in 193.2 seconds, 18494 bytes.
Sep 16 09:45:33 dolphin.dea.gr spamd[22184]: SIGPIPE received - reopening log so
cket
Sep 16 09:45:33 dolphin.dea.gr spamd[22186]: SIlast message repeated 2 times
Sep 16 09:45:34 dolphin.dea.gr spamd[22178]: clean message (-4.3/5.0) for clamav
:1180 in 234.2 seconds, 26354 bytes.
Sep 16 09:45:34 dolphin.dea.gr spamd[22178]: cllast message repeated 1 time
Sep 16 09:45:34 dolphin.dea.gr spamd[22178]: SIGPIPE received - reopening log so
cket
Sep 16 09:45:34 dolphin.dea.gr spamd[22187]: clean message (3.1/5.0) for clamav:
1180 in 178.8 seconds, 29683 bytes.
Sep 16 09:45:34 dolphin.dea.gr spamd[22187]: cllast message repeated 1 time
Sep 16 09:45:34 dolphin.dea.gr spamd[22187]: SIGPIPE received - reopening log so
cket

------------------ syslog ---------------------

We run 8 children proccesses. Normally spamd runs fine with scantimes 2-3
seconds even for 20-30k messages. But sometimes it gets very slow with responce
times even to 1000seconds for 2-3kb messages. 

The cofiguration for the mail-server is sendmail milter and milter-spamc. The
timeout (at sendmail.cf) is
 Xmilter-spamc, S=local:/var/clamav/milter-spamc.sock, T=S: 2m;R:4m

Finally, the deamon dies, with no syslog entry.
Comment 3 Justin Mason 2004-09-16 03:59:38 UTC 
could you try with the current 3.0.0 release candidate?   this should be fixed.
Comment 4 Michael Parker 2005-01-21 11:18:24 UTC 
Hearing nothing, assume all is well.  Feel free to re-open if this is still a
problem in 3.0+