/etc/init.d/spamassassin reload fails unless /var/run/spamd/ exists for pid file

Bug #1421787 reported by Fleish
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
spamassassin (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Spamassassin reload attempts to use pid from /var/run/spamd/spamd.pid. However, this directory is not created by the package, therefore the reload fails because it does not know the PID of the running process. Manually creating this directory, killing all running spamd processess, and calling /etc/init.d/spamassassin start fixes the issue. The spamassassin package should create this run directory it requires on installation.

Excerpt of /etc/init.d/spamassassin reload with missing directory:
Reloading SpamAssassin Mail Filter Daemon: + start-stop-daemon --stop --pidfile /var/run/spamd/spamd.pid --signal HUP --exec /usr/bin/perl
No /usr/bin/perl found running; none killed.

1)
Description: Ubuntu 12.04.5 LTS
Release: 12.04

2)
spamassassin:
  Installed: 3.3.2-2ubuntu1.1
  Candidate: 3.3.2-2ubuntu1.1
  Version table:
 *** 3.3.2-2ubuntu1.1 0
        500 http://mirror/ubuntu/ precise-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     3.3.2-2ubuntu1 0
        500 http://mirror/ubuntu/ precise/main amd64 Packages

3)
I expect a HUP signal to be sent to spamd parent PID

4)
No HUP signal is sent, because the script cannot determine the spamd parent PID

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in spamassassin (Ubuntu):
status: New → Confirmed
Revision history for this message
Sigmund (stormsh) wrote :

Hi there, I am working on this problem for a few weeks now. But I don't know much about linux so I have so dig in everytime. I posted my progress in detail in the parallels forum in hope for help. So I won't write it all here, because it's a lot I tried (because I didn't know where to start looking). If you read this and verify my progress with yours, that would be great, so I know I'm on the right way.

http://forum.sp.parallels.com/threads/spamd-sighup-not-working-options-changed.332300/

I did the changes you mentioned above and hope they work (I will see that tomorrow).

Revision history for this message
Sigmund (stormsh) wrote :

Hi there, I solved my problem with the spamassassin. It was a combination of more that one problem (anything else would be boring ;) ).
First one was the missing spamd.pid-file (solution see above).

Second: I changed "qmgr" and "pickup" at "/etc/postfix/master.cf".
qmgr fifo n - n 1 1 qmgr
pickup fifo n - - 60 1 pickup
It has to be "fifo" instead of "unix"? Then restart postfix ( service postfix restart or /etc/init.d/postfix restart ).
(http://forum.sp.parallels.com/threads/postfix-master-connection-refused.303699/)

Third and last I changed the rsyslog" at "/etc/logrotate.d to "solve issues with wrong owner rights after the logrotation"
from:
postrotate
reload rsyslog >/dev/null 2>&1 || true
endscript

to:
postrotate
reload rsyslog >/dev/null 2>&1 || true
endscript
su root root

And here is the long Version:
http://forum.sp.parallels.com/threads/spamd-sighup-not-working-options-changed.332300/

st.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.