Enable component-level debugging

In Oracle® Clusterware Administration and Deployment Guide 11g Release 2 (11.2), the section, Component Level Debugging, says that:

You can use crsctl set log and crsctl set trace commands as the root user to enable dynamic debugging for the Oracle Clusterware Cluster Ready Services (CRS), Cluster Synchronization Services (CSS), and the Event Manager (EVM).

Enabling Debugging for CRS, CSS, and EVM Modules

You can enable debugging for the CRS, CSS, and EVM modules and their components, and for resources, by setting environment variables or by issuing crsctl set log commands, using the following syntax:

crsctl set {log | trace} module_name
"component:debugging_level[,component:debugging_level][…]"

Run the crsctl set command as the root user, and supply the following information:

The following commands show examples of how to enable debugging for the various modules:

crsctl set log crs "CRSRTI:1,CRSCOMM:2"

crsctl set log crs "CRSRTI:1,CRSCOMM:2,OCRSRV:4"

crsctl set log evm "EVMCOMM:1"

crsctl set log res "resname:1"

To obtain a list of components that can be used for debugging, run the crsctl lsmodules command, as follows:

crsctl lsmodules {crs | css | evm}

Note:
You do not have to be the root user to run the crsctl lsmodules command.

Example 1

To set debugging levels on all cluster nodes, include the -all keyword, as follows:

crsctl set log crs "CRSRTI:1,CRSCOMM:2" -all

Example 2

To set debugging levels on specific cluster nodes, include the -nodelist keyword and the names of the nodes, as follows:

crsctl set log crs "CRSRTI:1,CRSCOMM:2" -nodelist node1,node2