[Bug 161785] spamassassin restart fails - functions bug?

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: spamassassin restart fails - functions bug?


https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=161785


menscher+rh at uiuc.edu changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |menscher+rh at uiuc.edu




------- Additional Comments From menscher+rh at uiuc.edu  2006-03-17 13:42 EST -------
I'm not so sure this is "fixed" in RHEL4U3.  We recently ran up2date on our
RHEL4 system, to bring it up to U3.  As part of the upgrade, we got a new
version of spamassassin:

spamassassin-3.0.5-3.el4         Thu 16 Mar 2006 05:34:40 PM CST

The install of other packages lasted until 05:49:10 PM, and then up2date
restarted all the daemons.  But our boot.log indicates spamd didn't restart
properly:

Mar 16 17:51:43 zeus spamassassin: spamd shutdown succeeded
Mar 16 17:51:44 zeus spamd: Could not create INET socket on 127.0.0.1:783:
Address already in use (IO::Socket::INET: Address already in use)
Mar 16 17:51:44 zeus spamassassin: spamd startup failed

The result was that everything worked fine for an hour, until the last child
exited due to the default --max-conn-per-child=200.  And then we got the mess of

Mar 16 18:46:30 zeus spamc[20565]: connect(AF_INET) to spamd at 127.0.0.1
failed, retrying (#1 of 3): Connection refused

At the time, ps output indicated no spamd processes running, and a
'/etc/init.d/spamassassin restart' worked fine to fix it.

I'm assuming that the restart would have used the newly-installed init script,
so that suggests that this fix was incomplete.  Or does the fix only work if
spamd was started using it (due to treatment of a pid file)?

-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.