rpc.statd is being started twice at boot time
Environment
Red Hat Enterprise Linux 6
NetworkManager configured to start at boot time
Issue
One instance is started by /etc/init.d/nfslock, called from /etc/rc.d/rc 5, which is expected. The other instance is via "mount -a -t nfs,nfs4" called via /etc/init.d/netfs which is called via the "/usr/libexec/nm-dispatcher.action", "/bin/sh /etc/NetworkManager/dispatcher.d/05-netfs eth0 up" chain. The mount command is calling mount.nfs which is launching "rpc.statd --no-notify".
How to stop the instance from /etc/init.d/netfs from starting ?
Resolution
- Red Hat's recommendation for enterprise class servers is to completely disable NetworkManager and just use the network-scripts functionality to manage network interfaces, this should stop the NetworkManager netfs chain from launching on init.
To disable NetworkManager from starting at boot
# service NetworkManager stop; chkconfig NetworkManager off
- And reconfigure networking to not use NetworkManager, by editing /etc/sysconfig/network-scripts/ifcfg-eth0 and changing NM_CONTROLLED=yes to NM_CONTROLLED=no. A back-up of these files outside of /etc/sysconfig/network-scripts/ is recommend before any changes.
Root Cause
This is because NetworkManager is running its own set of scripts in correlation with the sysconfig scripts normally generated.
Diagnostic Steps
- Verify if Networkmanager is configured to start at boot time,
# chkconfig --list NetworkManager
NetworkManager 0:off 1:off 2:on 3:on 4:on 5:on 6:off
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
