Description of problem: ypbind fails at boot because it cannot find the NIS server when using NetworkManager. After booting, starting ypbind works fine. If NetworkManager is disabled and network is enabled, ypbind will successfully start at boot. Version-Release number of selected component (if applicable): 0.7.1-4.git20090414.fc11 How reproducible: Consistently (on multiple machines).
Thanks for filling this bug. To get closer to your problem, can you pleas attach your /var/log/messages after boot with NM and also with s-c-n enabled? Thank you. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Created attachment 361435 [details] /var/log/messages with NetworkManager enabled
When I restart NetworkManager, it looks like this: [root@bolt ~]# service NetworkManager restart Stopping NetworkManager daemon: [ OK ] Setting network parameters... [ OK ] Starting NetworkManager daemon: [ OK ] [root@bolt ~]# r8169: eth0: link up Note the last message. This occurs a second or two after service has returned. It looks like NetworkManager is bringing up eth0 asynchronously--returning with "OK" before the network is necessarily available. And I think that if it's *not* available when ypbind starts (which it does immediately afterward during startup), ypbind fails. It certainly seems like NetworkManager shouldn't be returning with "OK" until the network is available for use.
NetworkManager is designed to bring interfaces up and down asynchronously; we need to penalize (or fix) the services that can't handle that instead of penalizing all services. There are two options: 1) Fix the ypbind initscript to block until the network is actually available 2) set NETWORKWAIT=yes in your /etc/sysconfig/network file Does #2 work for you?
Yes; adding NETWORKWAIT=yes works around the problem.
To fix this in yp-tools, maybe a dispatcher script would work to restart ypbind when the network situation changes. See initscripts (which drops /etc/NetworkManager/dispatcher.d/05-netfs onto the system) and 'man NetworkManager' for more information on dispatcher scripts.
(last comment more for yp-tools maintainer than for Braden)
Hi, ypbind should be able to handle the NetworkManager async startup now. When started, ypbind handles unavailable network just fine AFAIK. *** This bug has been marked as a duplicate of bug 480096 ***