What to check for NFSRestart Agent that complains about "0513-004 The Subsystem or Group, nfs_daemon, is currently inoperative".

book

Article ID: 100001456

calendar_today

Updated On:

Resolution

[ Common behavior of NFSRestart Agent in its online procedure ]
 
  1. Terminates statd and lockd.
  2. If the value of the NFSLockFailover attribute is 1, it copies the locks from the shared-storage to the /var/statmon/sm directory.
  3. Starts the statd and lockd daemons.
  4. Starts the smsyncd daemon to copy the contents of the /var/statmon/sm directory to the shared storage (LocksPathName) at regular, two-second intervals if the value of the NFSLockFailover attribute is1.

Note: If there are no lockfiles in the {$PATH}/.sm/sm directory, then trying to "mv {PATH}/.sm/sm* would fail in the engine log:

For example:
vioclient1:/var/tmp/veritas$ mv sm/sm/* test
mv: 0653-401Cannot rename sm/sm/* to test/*:
            A file or directory in the path name does not exist

whereas the engine log error is "No such file or directory"

 
[Explanation ]
These are the three daemons which the NFSRestart agent starts and monitors:
  1. rpc.lockd
  2. rpc.statd
  3. smsyncd

 

[Steps to check daemons relating to NFSRestart Agent]
  • If there was any problem with NFSRestart, please run those three daemons manually outside VCS and see if it continues to run. It is suspected there is a problem outside VCS.
  • If these daemons are not able to run outside VCS continuously, then the chance is that VCS will not be able to starts and monitors those either.
 
[Common messages ]
Wait for'Rebooting...' before stopping.
Errorreporting has stopped.
AdvancedAccounting has stopped...
Processaccounting has stopped.
nfs_clean:Stopping NFS/NIS Daemons
0513-004 TheSubsystem or Group, nfsd, is currently inoperative.
0513-004 TheSubsystem or Group, biod, is currently inoperative.
0513-004 TheSubsystem or Group, rpc.lockd, is currently inoperative.
0513-004 TheSubsystem or Group, rpc.statd, is currently inoperative.
0513-004 TheSubsystem or Group, gssd, is currently inoperative.
0513-004 TheSubsystem or Group, nfsrgyd, is currently inoperative.
0513-004 TheSubsystem or Group, rpc.mountd, is currently inoperative.
0513-004 TheSubsystem or Group, ypbind, is currently inoperative.
0513-044 Thexntpd Subsystem was requested to stop.
0513-044 Theaixmibd Subsystem was requested to stop.
0513-044 Thehostmibd Subsystem was requested to stop.
0513-044 Themuxatmd Subsystem was requested to stop.
 
Note: In case of any daemons pertaining to NFS complaining about the erroneous messages with "currently inoperative" as shown above.
 
If NFS and NFSRestart Agents are configured properly, it's normal messages while NFSRestart Agent becomes offline.
If not, please check out the step mentioned above.

Issue/Introduction

What to check for NFSRestart Agent that complains about "0513-004 The Subsystem or Group, nfs_daemon, is currently inoperative".
Powered by Wolken Software