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

 

2009/09/0113:00:19 VCS INFO V-16-2-13001 (system2) Resource(system1_TA_T_ST3): Output of the completed operation (monitor)

tom id=204pgrp=staff groups=staff home=/home/tom shell=/usr/bin/ksh login=true su=truerlogin=true daemon=true admin=false sugroups=ALL admgroups= tpath=nosak ttys=ALLexpires=0 auth1=SYSTEM auth2=NONE umask=22 registry=files SYSTEM=compatlogintimes= loginretries=0 pwdwarntime=0 account_locked=false minage=0 maxage=0maxexpired=-1 minalpha=0 minother=0 mindiff=0 maxrepeats=8 minlen=0 histexpire=0histsize=0 pwdchecks= dictionlist= fsize=2097151 cpu=-1 data=262144 stack=65536core=2097151 rss=65536 nofiles=2000 roles=

 

 

 

The problem occurs only if:

-On systems running AIX operating system

-Veritas Cluster Server 5.0 (or above) is installed

-Veritas Cluster Server 5.0 MP3 RP1 HF1a patch is NOT installed

-Application resource is owned by a non-root user

 

If the owne rof VCS Application resource is a non-root user, the application agent relies of user's home directory to monitor the resource correctly. It runs 'lsuser' to obtain this user information. By default the output of lsuser command is redirected to VCS engine log. This has caused VCS engine log to fill up rapidly.

Veritas VCS Engineering acknowledges this via internal etrack incident # 1836923 and has addressed the issue in the following releases.

VCS5.0MP3RP1HF1a (for AIX only)

VCS5.1 (Upcoming release for all Platforms)

 

Please use the below mentioned workaround for earlier releases of VCS or if you are unable to install the patch.

Edit the file "/opt/VRTSvcs/bin/Application/functions" on all nodes in the cluster a smentioned below:

Modify the following line in the function app_execmonprog() from:

to:

 

 

The fix is available in following releases.

VCS5.0MP3RP1HF1a (for AIX only)

VCS5.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).