Bug 6050 - Spamassassin sometimes dies with SIGPIPE
Summary: Spamassassin sometimes dies with SIGPIPE
Status: RESOLVED WORKSFORME
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: spamassassin (show other bugs)
Version: 3.2.5
Hardware: PC FreeBSD
: P5 major
Target Milestone: Undefined
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-25 13:25 UTC by kevin Atkinson
Modified: 2019-06-24 15:07 UTC (History)
2 users (show)


Attachment Type Modified Status Actions Submitter/CLA Status
Spamassassin log with debugging turned on text/plain None kevin Atkinson [NoCLA]
More logs, See comment #1 text/plain None kevin Atkinson [NoCLA]
Test log, where SA crashes at Razor text/plain None Ari Sovijärvi [NoCLA]
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 kevin Atkinson 2009-01-25 13:25:29 UTC 
Created attachment 4428 [details]
Spamassassin log with debugging turned on

Spamassassin sometimes dies with SIGPIPE for an unknown reason.  Based on the log my best guess is that it is during some network test.  When it will dies is unpredictable, because when I pass the same mail though again it sometimes is OK and other times its not. 

With the fix for #6033 this will cause mail to get unfiltered, without the fix it would cause me to lose mail.

OS: FreeBSD 6.2-PRERELEASE

Let me know if you need any additional info or what me to do something to help get better debug output or the like.
Comment 1 kevin Atkinson 2009-01-25 13:44:42 UTC 
It seams I can't reproduce the problem when running  manually Spamassassin or procmail manually.  I will attach another log message with Spamassassin being run on the same mail message.  The first it dies, the second time (running procmail manually) it didn't.

Also, here is the Perl version in case it helps.

  This is perl, v5.8.8 built for i386-freebsd-64int
  (with 1 registered patch, see perl -V for more detail)
Comment 2 kevin Atkinson 2009-01-25 13:48:46 UTC 
Created attachment 4429 [details]
More logs, See comment #1
Comment 3 Justin Mason 2009-01-26 03:05:10 UTC 
normally, AFAIK, SIGPIPE should only be delivered if a process writing _into_ SpamAssassin's stdin dies.  are you sure that's not what's happening?  that would explain why it's proving hard to reproduce.

also, it may be worth trying turning off pyzor, razor etc. one by one to see if you can narrow down which one is causing it, if it _is_ a network test at fault.
Comment 4 kevin Atkinson 2009-01-26 12:03:46 UTC 
Well the last debug message always is "[61264] dbg: info: entering helper-app run mode", when it dies.  This is defined is Dns.pm.

My best guess based on the logs is that it is razor2 which I turned off.  It will be a day or so until I can be sure that fixed it.
Comment 5 kevin Atkinson 2009-01-27 11:58:25 UTC 
Disabling razor2 seamed to have solved the problem....
Comment 6 Ari Sovijärvi 2009-02-05 04:34:27 UTC 
I also noticed this bug when I was investigating why an apparent spam message got through. This bug is apparently in Razor and it happens about 1 in 10 attempts. I've attached a log with "-D razor" parameter.

I'm running FreeBSD 7.1-RELEASE-p2 with Perl v5.8.9.
Comment 7 Ari Sovijärvi 2009-02-05 04:36:11 UTC 
Created attachment 4430 [details]
Test log, where SA crashes at Razor
Comment 8 Justin Mason 2009-02-05 05:27:51 UTC 
can anyone capture a -D debug log and an "strace -f" log of this happening? that may be able to demonstrate where/if the SIGPIPE handler is being messed with.
Comment 9 Henrik Krohns 2019-06-24 15:07:07 UTC 
Closing old bug, if it's still problem a decade later, feel free to post.. :-)