How to increase debug logging for a specific cluster resource in InfoScale Windows

book

Article ID: 100019999

calendar_today

Updated On:

Resolution

To increase the debug log level for a resource type, please select either Procedure A (performed in the Cluster Manager Console GUI) or Procedure B (performed from the Command Line Interface (CLI) ) below:
 
Procedure A:
  1. Launch the Cluster Manager - Java Console and login to the cluster that has the resource type where the debug logging is to be increased.
  2. Expand the Service Group that contains the resource type.
  3. In the left pane, select the resource type, such as the MountV resource type, and in the right pane, select the button Show all attributes (figure 1).

Figure 1
 
 

  1. Select the LogDbg attribute and select Edit
  2. Add one of  the following to the KeyList Values :
    • DBG_1
    • DBG_2
    • DBG_20
    • DBG_21

Note: The above values are the most commonly used values while debugging a resource type. The value to use should be specified by a Veritas Technical Support Engineer as different resource types utilize these values differently.

  1. Add one or more of the following to the KeyList Values :
    • DBG_AGINFO
    • DBG_AGDEBUG
    • DBG_AGTRACE

Note: The debug messages from the agent framework are logged with the above severities, with DBG_AGINFO providing the least information, and DBG_AGTRACE the most verbose. For high debugging levels you may specify all three valued items listed above within the KeyList Values.

Procedure B:


Below are the steps for implementing debug level logging via the CLI. This is a global setting and only needs to be done on one node in the cluster.

Increasing details in the MountV logs from a command prompt:
  1. # haconf -makerw
  2. # hatype -modify MountV LogDbg DBG_1 DBG_2 DBG_20 DBG_21 DBG_AGINFO DBG_AGDEBUG  DBG_AGTRACE
  3. # haconf -dump -makero

It is suggested that all debug logging is diabled after the issue has been reproduced and all necessary data has been collected for Veritas Support to review during troubleshooting practices. If debug logging has been implemented via the Cluster Manager Console GUI, simply reverse the steps performed above to disable the extensive debug logging. Use the following commands to terminate the debug logging session via a Command Prompt:

  1. # haconf -makerw
  2. # hatype -modify MountV LogDbg -delete -keys
  3. # haconf -dump -makero

Issue/Introduction

All InfoScale Windows cluster resources have a corresponding log file that logs when an error with the resource occurs. For example, the InfoScale MountV resource log, %vcs_home%\log\MountV_A.txt, will make an entry log if a MountV resource fails to online or offline on a node. When the default logging that is enabled for a resource does not provide enough information to troubleshoot the issue, the level of debug logging may need to be increased. This can be done using the LogDbg attribute for the resource. Changing the values of the LogDbg attribute is dynamic and does not require InfoScale or a resource to be restarted.
Powered by Wolken Software