Bug 504840 - ypbind won't start
Summary: ypbind won't start
Keywords:
Status: CLOSED DUPLICATE of bug 483650
Alias: None
Product: Fedora
Classification: Fedora
Component: ypbind
Version: 11
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Vitezslav Crhonek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-06-09 18:03 UTC by Tom Horsley
Modified: 2009-06-11 13:36 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-06-11 11:47:24 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Tom Horsley 2009-06-09 18:03:35 UTC 
Description of problem:

I just installed two different fedora 11 xen hvm virtual machines, one i386,
the other x86_64. On both of them, ypbind does this:

Starting NIS service:                                      [  OK  ]
Binding NIS service: ....................                  [FAILED]
Shutting down NIS service:                                 [  OK  ]

Similar virtual machines on the same xen host have no problems starting
ypbind with the same config info:

domain software server 129.134.30.36

Version-Release number of selected component (if applicable):
ypbind-1.20.4-18.fc11.x86_64
ypbind-1.20.4-18.fc11.i586

How reproducible:
every time

Steps to Reproduce:
1. see above
2.
3.
  
Actual results:
timeout at ypbind startup

Expected results:
ypbind starts normally

Additional info:
Comment 1 Vitezslav Crhonek 2009-06-11 11:46:30 UTC 
You should update to ypbind-1.20.4-19.fc11 (zero day update).

Or look at workaround here: https://bugzilla.redhat.com/show_bug.cgi?id=483650
Comment 2 Vitezslav Crhonek 2009-06-11 11:47:24 UTC 

*** This bug has been marked as a duplicate of bug 483650 ***
Comment 3 Tom Horsley 2009-06-11 13:36:00 UTC 
Yep, the new update worked (as did the work-around).
Note You need to log in before you can comment on or make changes to this bug.