Bug 216440 - rpc.statd ate my CUPS
Summary: rpc.statd ate my CUPS
Alias: None
Product: Fedora
Classification: Fedora
Component: nfs-utils
Version: 6
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Steve Dickson
QA Contact: Ben Levenson
Depends On:
TreeView+ depends on / blocked
Reported: 2006-11-20 14:49 UTC by Tim Smith
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2007-07-26 14:24:03 UTC

Attachments (Terms of Use)

Description Tim Smith 2006-11-20 14:49:29 UTC
Description of problem:
When a system has both NFS and CUPS, the nfslock service starts first during 
boot and always gets assigned port 631, which causes CUPS startup to fail.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Enable CUPS
2. Enable nfslock
3. Reboot
Actual results:
CUPS fails to start as port 631 already in use

Expected results:
CUPS should start

Additional info:
Could fix this by setting the port used by rpc.statd to a safe value with 
the -p option, or by moving CUPS before portmap in the boot sequence.
According to the manual page, rpc.statd requests a port from the portmapper. I 
don't see a way to tell the portmapper what range is acceptable though., so 
possibly this is a bug report/feature request for the portmapper.

Comment 1 Hansen Tanjung 2007-02-01 09:10:52 UTC
Yes, I can confirm this. This conflict beat my coworker computer twice at this week.

Comment 2 Steve Dickson 2007-03-12 17:38:38 UTC
You can explicitly set the port statd
will listen on by setting the STATD_PORT
variable in /var/sysconfig/nfs which
should help avoid this problem

Comment 3 Tim Smith 2007-05-25 07:43:56 UTC
That should work. This should be set by default though. It doesn't appear to 
be on by default in my FC6 setup.

Comment 4 Steve Dickson 2007-07-26 14:24:03 UTC
in more recent nfs-utils I've added a fully populated 
/etc/sysconfig/nfs file that should help... 

Comment 5 Hansen Tanjung 2007-07-27 02:49:00 UTC
is this backported for fc6 too?

Note You need to log in before you can comment on or make changes to this bug.