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

Solution Verified - Updated -

Issue

  • NFS resource fails to start, and pcs status output 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 status show NFS resource timeout failures
  • My nfsserver resource is taking a very long time to start
  • nfsserver resource won't start unless I set a very high op start timeout
  • nfsserver hangs waiting on a chcon every time I start it

Environment

  • Red Hat Enterprise Linux (RHEL) 6 or 7 with the High Availability Add-On
  • pacemaker
  • An nfsserver resource is configured and managed in the cluster
    • This nfsserver resource's nfs_shared_infodir points to a directory that has a large number of application/data files or directories in it

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content