How to enable additional debug logging for the HAD Engine and the VCS Agent issues

Article:TECH87874  |  Created: 2009-01-02  |  Updated: 2011-08-08  |  Article URL http://www.symantec.com/docs/TECH87874
Article Type
Technical Solution



Issue



How to enable and/or disable additional debug log level in the VCS Cluster for debugging the HAD Engine and the VCS Agent issues


Solution



How to enable additional debugging on the VCS Cluster for the HAD Engine and the VCS Agents

If the default logging in the /var/VRTSvcs/log/engine_A.log is not sufficient to provide an understanding of any problem in the Veritas Cluster Server or any of the VCS Agents, then extra debugging may need to be enabled for further troubleshooting of the issue to provide Symantec Technical Support with the required information on the VCS behavior in detail:

This can be done as follows using the appropriate Debug Levels as recommended by Technical Support.

The following example Debug Levels should be sufficient for basic troubleshooting. Engineering may require additional Log Levels depending upon different situations.

For debug to be enabled automatically for the VCS Engine at system boot time, edit the /opt/VRTSvcs/bin/vcsenv file and add the following entries as below:

VCS_DEBUG_LOG_TAGS="DBG_Policy,DBG_TRACE,DBG_AGTRACE,DBG_AGINFO,DBG_AGDEBUG"
export VCS_DEBUG_LOG_TAGS

To add and enable the debug levels immediately, execute the following commands:
(These steps will NOT automatically add the entry into /opt/VRTSvcs/bin/vcsenv)
eg:
# haconf -makerw
# halog -addtags DBG_POLICY
# halog -addtags DBG_TRACE
# halog -addtags DBG_AGTRACE
# halog -addtags DBG_AGINFO
# halog -addtags DBG_AGDEBUG
# haconf -dump -makero

To disable the debug levels for the VCS Engine, remove the entry for the Variable VCS_DEBUG_LOG_TAGS from the /opt/VRTSvcs/bin/vcsenv file.
To make the change immediate execute the following commands:
# haconf -makerw
# halog -deltags DBG_POLICY
# halog -deltags DBG_TRACE
# halog -deltags DBG_AGTRACE
# halog -deltags DBG_AGINFO
# halog -deltags DBG_AGDEBUG
# haconf -dump -makero

Similarly, we can enable additional debug levels for VCS Agents

Example to enable additional Debug level for Application Agent:
# haconf -makerw
# hatype -modify Application LogDbg -add DBG_1 DBG_2 DBG_3 DBG_4 DBG_5 DBG_AGDEBUG DBG_AGINFO DBG_AGTRACE
# haconf -dump -makero

To disable the debug levels for the VCS Agent:
Eg. To disable additional Debug level for Application Agent:
# haconf -makerw
# hatype -modify Application LogDbg -delete DBG_1 DBG_2 DBG_3 DBG_4 DBG_5 DBG_AGDEBUG DBG_AGINFO DBG_AGTRACE
# haconf -dump -makero

The current setting for the added tags can be displayed with:
# halog -info
Log on systemA:
        path = /var/VRTSvcs/log/engine_A.log
        maxsize = 33554432 bytes
        tags = DBG_AGTRACE, DBG_AGDEBUG, DBG_AGINFO, DBG_POLICY, DBG_TRACE
        flushtags = DBG_AGTRACE, DBG_AGDEBUG, DBG_AGINFO, DBG_POLICY, DBG_TRACE

# hatype -display Application -attribute LogDbg
#Type        Attribute              Value
Application  LogDbg                 DBG_1       DBG_2   DBG_3   DBG_4   DBG_5   DBG_AGDEBUG     DBG_AGINFO      DBG_AGTRACE


The additional Debug logging will increase the size of the information logged in the /var/VRTSvcs/log/engine_A.log and the Specific Agent Logs in the same /var/VRTSvcs/log directory if respective Agent debugging is increased along with the VCS Debug.

Please ensure that we have sufficient space in the /var partition for the extra logging. The Debug logging can be disabled once the logs are provided to the Technical Support Team.
 


Legacy ID



330585


Article URL http://www.symantec.com/docs/TECH87874


Terms of use for this information are found in Legal Notices