When monitoring NFS under VERITAS Cluster Server (VCS) the lockd process is not restarted if it dies.
The NFS agent starts /usr/lib/nfs/lockd when onlining, but does not monitor for it.
NOTE: The procedure in this TechNote creates a new agent (a copy of the Process agent) to monitor the lockd process, and restart it if necessary. For more information on creating agents, see the
VERITAS Cluster Server Agent Developer's Guide. When following this procedure, it is important to use the exact same capitalization as in the examples.
To have VCS monitor the lockd process:
1. Change into the VCS binary directory (do this on all systems).
2. Make a copy of the Process directory, named Lockd (do this for all systems).
#cp -rp Process Lockd
3. Change the name of the ProcessAgent to LockdAgent
15. Make the share type resources dependant on the lockd_res as they are with the NFS type resource.
#hares -link <share type resource> lockd_res
16. Save the new configuration and return the cluster configuration to read-only
#haconf -dump -makero
There should now be a new resource type named Lockd and a new resource named lockd_res. The existing share type resources should be dependant on the lockd_res. With this configured, if the /usr/lib/nfs/lockd process exits or is killed VCS will restart it.
Imported Document Id
This is machine translated content
Login to Subscribe
Please login to set up your subscription.
Didn't find the article you were looking for? Try these resources.