Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 83985 - ypbind grabbin g cups port
ypbind grabbin g cups port
Status: CLOSED DUPLICATE of bug 103401
Product: Red Hat Linux
Classification: Retired
Component: ypbind (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Steve Dickson
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2003-02-10 13:36 EST by Stephen John Smoogen
Modified: 2007-04-18 12:50 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 13:51:42 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Stephen John Smoogen 2003-02-10 13:36:51 EST
Description of problem:

cups will not start up on various Red Hat Linux 7.3 clients with updates.
Looking through netstat -natp we are seeing ypbind consistently binding to port
631 which is what IPP uses. 

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

cups-1.1.14-15.2   [and backport of rawhide cups]

How reproducible:

60% of 200 clients here are seeing it... have not figured out why 40% arent.

Here is the /etc/yp.conf with edits for security reasons (yyy|xxxx)

# /etc/yp.conf - ypbind configuration file
# Valid entries are
#       Use server HOSTNAME for the domain NISDOMAIN.
#domain NISDOMAIN broadcast
#       Use  broadcast  on  the local net for domain NISDOMAIN
#ypserver HOSTNAME
#       Use server HOSTNAME for the  local  domain.  The
#       IP-address of server must be listed in /etc/hosts.
domain yyy server yyy.xxxx.gov

Steps to Reproduce:
1. install 7.3
2. upgrade to latest updates
3. configure yp as above, and cups to browsepoll from specific machine
4. reboot
5. watch cups not be able to bind to port 631.
Comment 1 Miloslav Trmac 2003-12-03 15:19:07 EST
Duplicate of bug 78830
Triage->Duplicate 78830
Comment 2 Miloslav Trmac 2003-12-03 15:29:08 EST
This is actually a duplicate of bug 103401.
Triage->Duplicate 103401
Comment 3 Aleksey Nogin 2004-01-06 23:50:04 EST

*** This bug has been marked as a duplicate of 103401 ***
Comment 4 Red Hat Bugzilla 2006-02-21 13:51:42 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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