For some reason the spamassassin 3.0.2 build does not correctly create the needed pidfile so that the init script can stop the process Reproducible: Always Steps to Reproduce: 1. Start spamd /etc/init.d/spamd start 2. Stop spamd /etc/init.d/spamd {stop | restart} 3. Error spamd cannot be stopped Actual Results: The process was still in the background running Expected Results: All spamd process should be stopped I played with the spamd binary and saw that `spamd --pidfile /var/run/spamd.pid` is not created. As a temporary workaround I have added to the spamd init.d script as the last action before the start() block ends: echo "`pidof spamd`" > /var/run/spamd.pid
Probably bug 4074 (see URL) in the upstream Bugzilla.
I'm also observing the same problem with my upgrade from spamassassin v2.64 to v3.0.2 and wanted to add some information to this bug. I'm running with qmail/vpopmail, using the following startup options, "-x -v -u vpopmail -m 5 -c -H" -- perhaps the "-u vpopmail" is unnecessary, but none the less, it would still be an issue because spamd would try to run as some other user than root. Here is what syslog is reporting: Jan 26 22:29:03 bob spamd[6914]: server started on port 783/tcp (running version 3.0.2-gr0) Jan 26 22:29:03 bob spamd[6914]: server successfully spawned child process, pid 6919 Jan 26 22:29:03 bob spamd[6914]: server successfully spawned child process, pid 6920 Jan 26 22:29:03 bob spamd[6914]: server successfully spawned child process, pid 6921 Jan 26 22:29:03 bob spamd[6914]: server successfully spawned child process, pid 6922 Jan 26 22:29:03 bob spamd[6914]: server successfully spawned child process, pid 6923 Jan 26 22:29:03 bob spamd[6914]: Can't write to PID file: Permission denied I solved the issue by creating a directory "/var/run/spamd", and chowned it vpopmail:vpopmail. I then modified the "/etc/init.d/spamd" script such that the pidfile variable now looked like this: pidfile=/var/run/spamd/spamd.pid Hope this helps.
Hi, That is my setup as well
I have the same problem with spamassassin 3.0.4, as a workaround I also created /var/run/spamd chowned to vpopmail:vpopmail and point the pid file into that directory. When will this be corrected??? We're now on version 3.0.4!
*** This bug has been marked as a duplicate of 70124 ***
