What order the nfsnotify resource should start in an NFS resource group in pacemaker cluster
Issue
- nfsnotify resource is not starting up in pacemaker cluster.
- In what order should I start the nfsnotify resource in an NFS resource group?
- nfsnotify resource fails to start with the below Failed Actions in pcs status output:
Failed Actions:
* nfs-notify_start_0 on node1.example.com 'unknown error' (1): call=168, status=complete, exitreason='sm-notify with source host set to [ <source-host-IP> ] failed. view syslog for more information'
Environment
- Red Hat Enterprise Linux 7 (with High Availability Add-On)
- pacemaker
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.
