Red Hat Bugzilla – Bug 195906
ypbind service fails to start and times-out with YPBINDPROC_DOMAIN: Domain not bound
Last modified: 2007-11-30 17:11:35 EST
Description of problem: NIS/yp service fails to start on boot-up on FC5 pentium lap-top with fully updated FC5 (not with development or test packages, though, just released updates.) I'm not sure which package update broke yp, becasue the pm-suspend and pm-hibernate work so well nowadays that I haven't rebooted for ages. Nothing has changed on our yp server. Version-Release number of selected component (if applicable): ypbind-1.19-0.i386.rpm (but this has not changed recently) How reproducible: 100% Steps to Reproduce: 1. Boot machine 2. Attempts to start NIS 3. Says YPBINDPROC_DOMAIN: Domain not bound lots of times then gives up Actual results: YPBINDPROC_DOMAIN: Domain not bound error message Expected results: Brief pause while NIS client registers with YP server. Additional info: This appears to be something that has broken in the last week's worth of FC5 updates. /etc/yp.conf says: domain eng.pto.optronics.co.uk server <ip number> (with the ip number filled in, obviously.) /etc/sysconfig/network/network contains the domain name too. None of this has changed. Last week NIS was ok; this week: Broken.
What is the output of 'domainname' ?
domainname returns the expected NIS domain = eng.pto.optronics.co.uk
Is there anything in /var/log/messags what would give a clue as to what broke?
This problem has become unreproduceable since I changed the network cable on the machine. Has anyone else confirmed the problem? If not, I suggest we close the bugzilla report. I'm rather surprised that a simple cable could cause such a behaviourally complex problem.