Bug 4074 - Spamd not creating PIDFILE
Summary: Spamd not creating PIDFILE
Status: RESOLVED FIXED
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: spamc/spamd (show other bugs)
Version: 3.0.2
Hardware: Other Linux
: P5 minor
Target Milestone: Undefined
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords: triage
Depends on:
Blocks:
 
Reported: 2005-01-12 07:06 UTC by Joseph
Modified: 2005-07-02 15:02 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 Joseph 2005-01-12 07:06:31 UTC 
I am running Slackware 10 and SpamAssassin 3.02.  When I start spamd via the 
slackware-spamd.rc file that is included with the spamassassin distro spamd 
does not create the PIDFILE /var/run/spamd.pid.  As a result I have to manually 
create the pidfile in order to stop spamassassin or restart it if I make a 
change to the local.cf file.  Any ideas?
Comment 1 Daryl C. W. O'Shea 2005-01-12 11:15:49 UTC 
spamd warns if it can't write to the default or specified PID file.  Check your
maillog (or wherever spamd logs) for a "Can't write to PID file:" warning after
starting spamd.

Starting spamd directly, without daemonizing it, should print this warning to
STDERR.

Let us know what you find.


Daryl
Comment 2 Joseph 2005-01-12 11:41:25 UTC 
That is the wierd part, once spamd starts its runs fine without the pid.  There 
is no error what so ever involving the pidfile until I try to restart or stop 
spamd. While spamd is running the maillog shows that spamd is running properlly 
and even shows which message is being scanned and what the score is.  Even 
running spamd without the daemon shows the same thing with no mention of the 
pidfile being missing.  I was playing around with some of the settings due to 
spamd causing a very large spike in I/O wait causing the machine to slow to a 
crawl.  I disabled logging completely by setting -s null then I got the PIDFILE 
missing error on startup.  So I set spamd to -s stderr 2>/dev/null, and started 
again and it started fine, again with no mention of the pidfile missing.
Comment 3 Bob Menschel 2005-04-30 20:34:01 UTC 
Query sent to Joseph.
Comment 4 Bob Menschel 2005-05-03 18:21:55 UTC 
Response from Joseph: 

> The problem disappeared when I installed the beta release of SpamAssassin. I
am no longer having this issue, but when I revert back to 3.0.3 the problem
reappears on one system only, but works fine on another running the same os and
packages as the one in question.

Therefore problem seems to still plague 3.0.3 unpredictably, but seems fixed in
3.1.0
Comment 5 Bob Menschel 2005-07-02 23:02:00 UTC 
Triage: closing as fixed since it appears to be fixed in 3.1.0.