NFSRestart is FAULTED when VCS_LOG is changed
Article ID: 100012736
Updated On:
Description
Error Message
##### snip /tmp/VRTSvcs/log/engine_A.log #####
VCS ERROR V-16-2-13066 (hostname) Agent is calling clean for resource(nfs_restart_L) because the resource is not up even after online completed.
VCS INFO V-16-2-13068 (hostname) Resource(nfs_restart_L) - clean completed successfully.
VCS INFO V-16-2-13071 (hostname) Resource(nfs_restart_L): reached OnlineRetryLimit(0).
VCS ERROR V-16-1-54031 Resource nfs_restart_L (Owner: Unspecified, Group: test-sg) is FAULTED on sys hostname
##### snip /tmp/VRTSvcs/log/engine_A.log #####
Cause
After set VCS_LOG="/tmp/VRTSvcs, The NFSRestart agent was still checking /var/VRTSvcs/lock/volatile.
Actually, lock file was created on /tmp/VRTSvcs/lock/volatile.
##### snip /tmp/VRTSvcs/log/NFSRestart_A.log #####
VCS DBG_3 V-16-50-0 NFSRestart:nfs_restart:monitor:Status file [/var/VRTSvcs/lock/volatile/.nfsrestart_nfs_restart_state] for resource [nfs_restart] is NOT present.
NFSRestart.C:status_file_present[182]
##### snip /tmp/VRTSvcs2/log/NFSRestart_A.log #####
Resolution
There is no solution for this issue.
Return the setting to default value(/var/VRTSvcs).
This will be fixed in VCS6.2
Applies To
VCS 5.1 , 6.0.x , 6.1.x for Solaris , Linux
Issue/Introduction
NFSRestart is FAULTED when VCS_LOG is changed.
NFSRestart is not only but also some VCS agents and modules are affected. Root directory for log files can be changed by VCS_LOG Environment Variable.
##### snip /opt/VRTSvcs/bin/vcsenv #####
VCS_LOG="/tmp/VRTSvcs"
export VCS_LOG
##### snip /opt/VRTSvcs/bin/vcsenv #####
