Bug 218216

Summary: spamd frequently can't bind to port 783
Product: [Fedora] Fedora Reporter: chris
Component: spamassassinAssignee: Warren Togami <wtogami>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6CC: felicity, jm, parkerm, perl-devel, reg+redhat, wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-12-10 15:30:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description chris 2006-12-03 16:47:11 UTC 
The default startup priority for nfslock is 14, and for spamassassin is 78. 
This means that rpc.statd is started up before spamd.

I'm regularly finding that rpc.statd decides to bind to port 783, which then
means spamd is unable to bind to that port and exits with "spamd: could not
create INET socket on 127.0.0.1:783: Address already in use".  This in turn
means I get swamped with spam!

I'm not sure whether this is primarily an issue with rpc.statd or with
spamassassin, but it'd be good to be able to persuade rpc.statd not to steal
that port before spamd gets a chance to bind to it.

Is this occurring because spamd doesn't have an entry in /etc/services, or would
that make no difference?

Changing the startup priorities so that spamd starts up before rpc.statd would
be a workaround, but it's a hack.  There must be a better solution.

Using spamassassin-3.1.7-1.fc6 and nfs-utils-1.0.10-4.fc6.

Thanks.
Comment 1 chris 2006-12-10 15:30:04 UTC 
Sorry - just realised this is effectively a duplicate of bug #103401 (which was
opened over 3 years ago...)

*** This bug has been marked as a duplicate of 103401 ***