Bug 189144 - rpc.statd sometimes binds to cups port 631
Summary: rpc.statd sometimes binds to cups port 631
Keywords:
Status: CLOSED DUPLICATE of bug 103401
Alias: None
Product: Fedora
Classification: Fedora
Component: nfs-utils
Version: 5
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Steve Dickson
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-04-17 16:45 UTC by Steve Wardell
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-05-16 15:51:09 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Steve Wardell 2006-04-17 16:45:07 UTC
Description of problem:
Last night I was having problems printing and found the following in the error log:
E [17/Apr/2006:01:33:03 -0400] StartBrowsing: Unable to bind broadcast socket -
Address already in use.

It seems that rpc.statd had bound to udp port 631. As 631 is the port cups uses,
cups was unable to start up.

Version-Release number of selected component (if applicable):
1.0.8.rc2-4.FC5.2

How reproducible:
Not sure but the situation is pretty straight forward about what's happening.

Steps to Reproduce:
1. Startup system
2. If rpc.statd does show in a netstat -anp as having bound to port 631, reboot
until it takes port 631
3. Start up cups
  
Actual results:
Cups gives the error message:
E [17/Apr/2006:01:33:03 -0400] StartBrowsing: Unable to bind broadcast socket -
Address already in use.

Expected results:
Cups would start up correctly as rpc.statd would not bind to port 631.

Additional info:
As a workaround, on a reboot after the erorr, rpc.statd bound to port 637 and
all was fine. rpc.statd should not bind to port 631.

Comment 1 Calvin Smith 2006-05-16 14:40:17 UTC
This is a known issue described in more detail in bug #103401

Comment 2 Tim Waugh 2006-05-16 15:51:09 UTC

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


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