Re: Spamassassin not working after update to 2010.1

On Sun, 2010-10-10 at 18:16 -0700, David Guntner wrote:
> David Guntner grabbed a keyboard and wrote:
> > Chris grabbed a keyboard and wrote:
> >> On Sun, 2010-10-10 at 03:06 -0700, David Guntner wrote:
> >>> I just updated from 2010.0 to 2010.1, and have discovered that
> >>> spamassassin (spamd) isn't running on my system.  Trying to start it get
> >>> messages like this:
> >>>
> >>> Starting spamd: Oct 10 03:04:27.117 [16785] warn: server socket setup
> >>> failed, retry 1: spamd: could not create INET socket on 127.0.0.1:783:
> >>> Address already in use
> >>> Oct 10 03:04:28.118 [16785] warn: server socket setup failed, retry 2:
> >>> spamd: could not create INET socket on 127.0.0.1:783: Address already in use
> >>>
> >>> etc.
> >>>
> >>> I've already checked and there isn't already an instance of spamd
> >>> running.  Doing a "netstat -apt|grep 783" shows that there's nothing
> >>> else that actually has that port.
> >>>
> >>> So, anyone have any ideas what's actually causing this and more
> >>> importantly, how to fix it?
> >>
> >> Dave, just for the heck of it run as root:
> >>
> >> [root@localhost ~]# service spamassassin stop
> >> Shutting down spamd:                                            [  OK  ]
> >> [root@localhost ~]# service spamassassin start
> >> Starting spamd:                                                 [  OK  ]
> >> [root@localhost ~]# 
> >>
> >> and see if that fixes your problem. 
> > 
> > There appears to no longer be a "spamassassin" service in /etc/init.d;
> > it would appear to be replaced by spamd as the service name.  And any
> > attempt to start that results in the error messages I reported. :-(  It
> > repeats that message for a few times, and then just quits.  So I
> > currently have no spamassassin protection on my machine.
> 
> Well, as luck would have it, I did some more searching - turns out that
> as of 2010.1, /etc/services names port 783 as "spamd" for Spamassassin,
> which is why my "netstat -apt|egrep 783" didn't turn up anything. :-)
> When changing that grep to look for "spamd" instead, I found that
> rpc.rquotad had somehow been attached to that port!  WTF?  Not exactly
> sure how *that* happened, and would sure like to know what I need to do
> in order to keep that from happening again next boot-up.....
> 
> I killed the process (not exactly sure how to restart it...) and then
> started up spamd again, and then it attached correctly and started right up.
> 
> So at least *part* of the mystery has been solved.... :-)
> 
>                   --Dave
> 

Sorry for the late reply Dave, trying to get out of here for a funeral,
are you sure you don't have in /etc/rc.d/init.d a script called
'spamassassin'?

Make a backup of it then rename it to spamassassin and see what
happens. 

-- 
Chris
KeyID 0xE372A7DA98E6705C

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEABECAAYFAkyy99IACgkQ43Kn2pjmcFzOaACfU1md19uG7v8pvuD5qKRLN5I4
FLoAn0pCdk1qlVdDf0pLkMvyeqe/bi7j
=FfU+
-----END PGP SIGNATURE-----