nfsserver cluster resource hit ERROR: No init script or systemd unit file detected for nfs server

Solution Verified - Updated -

Issue

  • Failover event occurred after cluster node hit error below
Apr 28 01:19:44 node1 nfsserver(DATASTORE-NFS)[46847]: ERROR: No init script or systemd unit file detected for nfs server 
Apr 28 01:20:29 node1 lrmd[39423]:  notice: DATASTORE-NFS_monitor_300000:46847:stderr [ Failed to list unit files: Connection timed out ]  
Apr 28 01:20:29 node1 lrmd[39423]:  notice: DATASTORE-NFS_monitor_300000:46847:stderr [ ocf-exit-reason:No init script or systemd unit file detected for nfs server ]
Apr 28 01:20:29 node1 crmd[39426]:  notice: datastore-s1-ha-DATASTORE-NFS_monitor_300000:222 [ Failed to list unit files: Connection timed out\nocf-exit-reason:No init script or systemd unit file detected for nfs server\n ]
Apr 28 01:20:29 node1 crmd[39426]:  notice: State transition S_IDLE -> S_POLICY_ENGINE
Apr 28 01:20:29 node1 pengine[39425]:  notice: On loss of CCM Quorum: Ignore
Apr 28 01:20:29 node1 pengine[39425]: warning: Processing failed monitor of DATASTORE-NFS on datastore-s1-ha: not installed  
Apr 28 01:20:29 node1 pengine[39425]:  notice: Preventing DATASTORE-NFS from re-starting on datastore-s1-ha: operation monitor failed 'not installed' (5)
Apr 28 01:20:29 node1 pengine[39425]:  notice:  * Move       OVIP                     ( datastore-s1-ha -> datastore-s2-ha )  

Environment

  • Red Hat Enterprise Linux 7
  • High Availability Add-on
  • sgi-nfs-utils-* (HP)

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