You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by "Diffenderfer, Randy" <ra...@eds.com> on 2005/03/07 19:57:51 UTC

Problem getting SA 3.0.2 to restart

Folks:

I invoke spamd using the following command line (as root):

/path/to/spamd -d -x -L -u sauser -s local2 -r
/var/run/spamassassin/spamd.pid

The pid directory is accessible/writable by the sauser and the file does get
created with contents as expected.

I try to force a reload by sending a SIGHUP to the process noted in
spamd.pid.  The logs reflect spamd closing down and trying to start up, but
it never gets up again...

<log snip>
Mar  4 16:32:09 ahtst2 spamd[6333]: server started on port 783/tcp (running
version 3.0.2)
Mar  4 16:32:09 ahtst2 spamd[6333]: server successfully spawned child
process, pid 6334
Mar  4 16:32:09 ahtst2 spamd[6333]: server successfully spawned child
process, pid 6335
Mar  4 16:32:09 ahtst2 spamd[6333]: server successfully spawned child
process, pid 6336
Mar  4 16:32:09 ahtst2 spamd[6333]: server successfully spawned child
process, pid 6337
Mar  4 16:32:09 ahtst2 spamd[6333]: server successfully spawned child
process, pid 6338
Mar  4 16:32:47 ahtst2 spamd[6333]: server hit by SIGHUP, restarting
Mar  4 16:32:47 ahtst2 spamd[6333]: child 6334 killed successfully
Mar  4 16:32:47 ahtst2 spamd[6333]: child 6335 killed successfully
Mar  4 16:32:47 ahtst2 spamd[6333]: child 6336 killed successfully
Mar  4 16:32:47 ahtst2 spamd[6333]: child 6337 killed successfully
Mar  4 16:32:47 ahtst2 spamd[6333]: child 6338 killed successfully
Mar  4 16:32:48 ahtst2 spamd[6333]: spamd starting
<end of log snip>

This is what I *don't* see (a usccessful startup):

<log snip>
Mar  4 16:34:41 ahtst2 spamd[6388]: spamd starting
Mar  4 16:34:42 ahtst2 spamd[6390]: server started on port 783/tcp (running
version 3.0.2)
Mar  4 16:34:42 ahtst2 spamd[6390]: server successfully spawned child
process, pid 6391
Mar  4 16:34:42 ahtst2 spamd[6390]: server successfully spawned child
process, pid 6392
Mar  4 16:34:42 ahtst2 spamd[6390]: server successfully spawned child
process, pid 6393
Mar  4 16:34:42 ahtst2 spamd[6390]: server successfully spawned child
process, pid 6394
Mar  4 16:34:42 ahtst2 spamd[6390]: server successfully spawned child
process, pid 6395
<end of log snip>

Anybody else have similar experiences?

rnd

Re: Problem getting SA 3.0.2 to restart

Posted by Theo Van Dinter <fe...@kluge.net>.
On Mon, Mar 07, 2005 at 01:57:51PM -0500, Diffenderfer, Randy wrote:
> I invoke spamd using the following command line (as root):
> 
> /path/to/spamd -d -x -L -u sauser -s local2 -r
> /var/run/spamassassin/spamd.pid
> 
> I try to force a reload by sending a SIGHUP to the process noted in
> spamd.pid.  The logs reflect spamd closing down and trying to start up, but
> it never gets up again...

It's in the spamd docs, although not very clearly unfortunately:

Note: If spamd is set to run as a non-root user (-u), and is to run on
a privileged port (any < 1024), the parent will not be able to be sent
a SIGHUP to reload the configuration.


This is, in theory, fixed in 3.1 (development), fwiw.

-- 
Randomly Generated Tagline:
"... as you go forth today ... or fifth, depending on your order in line ..."
                      - From the movie "Toys"