Bug 4846 - spamd: accidental fork:
Summary: spamd: accidental fork:
Status: NEW
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: spamc/spamd (show other bugs)
Version: 3.1.1
Hardware: Sun Solaris
: P5 normal
Target Milestone: Undefined
Assignee: SpamAssassin Developer Mailing List
Depends on:
Reported: 2006-03-29 20:43 UTC by Tom Schulz
Modified: 2006-03-29 12:52 UTC (History)
0 users

Attachment Type Modified Status Actions Submitter/CLA Status
Section of the log file text/plain None Tom Schulz [NoCLA]

Note You need to log in before you can comment on or make changes to this bug.
Description Tom Schulz 2006-03-29 20:43:38 UTC
Last week I noticed that many messages were comming through without being
processed by spamd.  After restarting spamd, everything went back to normal.
I just now found time to look in the log and found many lines like this:

spamd: accidental fork: 1487 != 416 at /usr/bin/spamd line 1382.

Starting about the same time there were complaints about dcc such as:

dcc: check failed: Insecure directory in $ENV{PATH} while running setgid
 at /opt/perl/lib/site_perl/5.8.5/Mail/SpamAssassin/Util.pm line 1299.
dcc: check failed: failed to read header

I will attach a section of the log file starting at the time of the first
error message.
Comment 1 Tom Schulz 2006-03-29 20:52:19 UTC
Created attachment 3436 [details]
Section of the log file

This was extracted from syslog with 'grep spamd'.  The rest of the log
continues with the same messages repeated but with different process id's
until I restarted spamd.  As far as I know, this has never happened before
and it has not happened since.