nfsnotify resource fails to start with 'unknown error' and logs show "sm-notify[<pid>]: my_name 'X.X.X.X' is unusable: Name or service not known" in a RHEL 6 or 7 High Availability cluster with pacemaker
Issue
- The
nfsnotifyresource I've configured won't start, andpcs statusshows 'unknown error'
Failed actions:
notify173_start_0 on rhel6-node2-pcmk.example.com 'unknown error' (1): call=167, status=complete, last-rc-change='Tue Jan 20 15:51:14 2015', queued=0ms, exec=95ms
notify173_start_0 on rhel6-node1-pcmk.example.com 'unknown error' (1): call=239, status=complete, last-rc-change='Tue Jan 20 15:51:06 2015', queued=0ms, exec=108ms
- When I start my NFS resource group, the
nfsnotifyresource doesn't start and the logs show an error fromsm-notify~
Jan 20 16:06:59 rhel6-node1-pcmk sm-notify[23339]: Version 1.2.3 starting
Jan 20 16:06:59 rhel6-node1-pcmk sm-notify[23339]: my_name '192.168.143.173' is unusable: Name or service not known
Environment
- Red Hat Enterprise Linux (RHEL) 6 or 7 with the High Availability Add On
pacemaker- One or more
nfsnotifyresources configured in the cluster CIB- A
nfsnotifyresource configured with asource_hostattribute value of an IP address, as opposed to a hostname
- A
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Close
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.