Bug 83985

Summary: ypbind grabbin g cups port
Product: [Retired] Red Hat Linux Reporter: Stephen John Smoogen <smooge>
Component: ypbindAssignee: Steve Dickson <steved>
Status: CLOSED DUPLICATE QA Contact: Ben Levenson <benl>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.3CC: aleksey
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-02-21 18:51:42 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 Stephen John Smoogen 2003-02-10 18:36:51 UTC 
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):

ypbind-1.10-7
kernel-2.4.18-24.7.x
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
#
#domain NISDOMAIN server HOSTNAME
#       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 20:19:07 UTC 
Duplicate of bug 78830
Triage->Duplicate 78830
Comment 2 Miloslav Trmac 2003-12-03 20:29:08 UTC 
Sorry.
This is actually a duplicate of bug 103401.
Triage->Duplicate 103401
Comment 3 Aleksey Nogin 2004-01-07 04:50:04 UTC 

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