nfsserver resource fails to start with a timeout or takes an excessive amount of time to start in a RHEL 6 or 7 High Availability cluster with pacemaker
Issue
- NFS resource fails to start, and
pcs statusoutput shows "Timed Out" errors for start operations on all nodes
Failed Actions:
* nfs-daemon_start_0 on node1 'unknown error' (1): call=36, status=Timed Out, exitreason='none',
last-rc-change='Mon Oct 31 10:26:10 2016', queued=0ms, exec=120002ms
* nfs-daemon_start_0 on node2 'unknown error' (1): call=36, status=Timed Out, exitreason='none',
last-rc-change='Mon Oct 31 10:24:03 2016', queued=0ms, exec=120002ms
pcs statusshow NFS resource timeout failures- My
nfsserverresource is taking a very long time to start nfsserverresource won't start unless I set a very highop start timeoutnfsserverhangs waiting on achconevery time I start it
Environment
- Red Hat Enterprise Linux (RHEL) 6 or 7 with the High Availability Add-On
pacemaker- An
nfsserverresource is configured and managed in the cluster- This
nfsserverresource'snfs_shared_infodirpoints to a directory that has a large number of application/data files or directories in it
- This
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
