Red Hat Bugzilla – Bug 814133
NFS and LDAP do not work because network is not up yet
Last modified: 2013-02-19 13:19:49 EST
Description of problem:
On all our machines we have the problem that most of the time NFS fails to mount and LDAP fails to authenticate, because the network is not up at the time it is required (that is our assumption, at least). We have to workaround this with two lines in /etc/rc.local:
service netfs restart
service nslcd restart
Version-Release number of selected component (if applicable):
Install nss-pam-ldapd and setup LDAP using authconfig with forcelegacy.
Setup some NFS mounts in /etc/fstab.
Boot your computer and observe that NFS dirs are not mounted, authentication and uid/gid-to-name solution does not work.
# chkconfig NetworkManager off
# chkconfig --del NetworkManager
This workaround still only works most of the time, because sometimes the network interface fails to get a carrier signal in time, and dhcp fails.
Another thing to try is putting NETWORKWAIT=true into /etc/sysconfig/network; that'll make the initscripts wait for NM to bring up the network, or 30 seconds, whichever happens first. That basically switches on the old behavior of waiting for a network interface to start up before continuing with the bootup.
Putting NETWORKWAIT=yes into /etc/sysconfig/network works.
Gentoo/Linux sets the status of the NetworkManager service to "starting" (instead of "stopped" or "started") until the network is announced as up by nm-online - this way the init system (OpenRC) will know that it has to wait until it may start other services depending on the network. Maybe that would be an option for RHEL, too?
Since RHEL 6.3 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
The problem in RHEL6 is that the init system is simply not intelligent enough to handle dependencies and parallelizing scripts. That's fixed in later releases with systemd, where this is not a problem.
Unfortunately, since sysvinit is pretty dumb, and everything is serialized with hardcoded dependencies, there's no other way to fix it except with NETWORKWAIT.
(In reply to comment #5)
> The problem in RHEL6 is that the init system is simply not intelligent
> enough to handle dependencies and parallelizing scripts. That's fixed in
> later releases with systemd, where this is not a problem.
> Unfortunately, since sysvinit is pretty dumb, and everything is serialized
> with hardcoded dependencies, there's no other way to fix it except with
Thanks for your answer!