nfsserver resource with a modified rpcpipefs_dir attribute fails to start with error "Failed to start NFS server locking daemons" in a RHEL 7 High Availability cluster

Solution Unverified - Updated -

Issue

  • My nfsserver resource won't start, citing "Failed to start NFS server locking daemons"
  • pcs status shows an error for the nfsserver resource about the lock daemons
Failed Actions:
* nfs-daemon_start_0 on node1.example.com 'unknown error' (1): call=340, status=complete, exitreason='Failed to start NFS server locking daemons',
    last-rc-change='Thu Jan  5 16:21:54 2017', queued=0ms, exec=403ms

Environment

  • Red Hat Enterprise Linux (RHEL) 7 with the High Availability Add-On
  • An nfsserver resource managed by the cluster
    • The rpcpipefs_dir attribute on that resource is set to something other than the default of /var/lib/nfs/rpc_pipefs

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.