Monitor of VCS Application resource returns UNKNOWN state. Errors out with "/opt/VRTSvcs/bin/Application/monitor[130]: RC: not found".

  • Article ID:100022044
  • Modified Date:
  • Product(s):

Problem

Monitor of VCS Application resource returns UNKNOWN state. Errors out with "/opt/VRTSvcs/bin/Application/monitor[130]: RC: not found".

Solution

ISSUE:
VCS Application resource monitoring returns UNKNOWN state if the "options" string for 'su' command is not populated.

EXACT ERROR MESSAGE:
2009/09/01 13:00:19 VCS INFO V-16-2-13001 (system2) Resource(system1_TA_T_ST3): Output of the completed operation (monitor)
[...]
/opt/VRTSvcs/bin/Application/monitor[130]: RC: not found


PROBLEM DESCRIPTION:
In one situation, the home directory of VCS application resource owner is configured in a failover service group. If the home directory is not available on the standby node, VCS Application agent does not monitor the resource correctly and may error out with messages similar to above.

CAUSE:
Veritas VCS Engineering acknowledges this defect via internal etrack incident # 1833669 and has addressed in the issue in following releases.
VCS 5.0MP3RP1HF1a (for AIX only)
VCS 5.1 (Upcoming release for all Platforms)


WORKAROUND:
Step-1:
Edit the file "/opt/VRTSvcs/bin/ag_i18n_inc.sh" on all nodes in the cluster as mentioned below:
Modify the following line in the function VCSAG_SU () from:
su "${OPTIONS.EN_US}" "${USER.EN_US}" -c "${COMMAND.EN_US}"; retval=$?
to:
su ${OPTIONS.EN_US} "${USER.EN_US}" -c "${COMMAND.EN_US}"; retval=$?

Step-2:
Edit the file "/opt/VRTSvcs/bin/Application/functions" on all nodes in the cluster as mentioned below:
Modify the following line in the function app_execmonprog() from:
RC = $?
to:
RC=$?


SOLUTION:
The fix is available in following releases.
VCS 5.0MP3RP1HF1a (for AIX only)
VCS 5.1 (Upcoming release for all Platforms)

Veritas Cluster Server 5.0 MP3 HF1a for AIX patch can be downloaded from Patch Central Web Site (Please see Related Documents section).

Related Articles

VCS engine log is filled with Application resource user (lsuser) information during every monitor cycle

Was this content helpful?

Get Support