You did not specify which version of Serviceguard is used.
The cmsetlog command (obsolete with SG A.11.19) enables users to obtain a more verbose output of cmcld. This is extremely useful if a problem should be reproduced. cmsetlog allows to set the log level and to restrict logging to specific categories and modules.
From SG A.11.19 onwards you can start logging for cmcld by adding the following lines in the /etc/cmcluster.conf and do a kill -SIGHUP .
You can also enable debug logging for a specific module only by setting in the same file:
CMCLD_{module mnemonic}_LOG_LEVEL=5
where {module mnemonic} is one of the following:
ATN = Auto Trans CDB = Configuration Database CLM = Cluster Management CMD = Commands CML = SAF Distributed Lock Service CMP = Config/Status Proxy CMS = SAF Cluster Membership Service CNF = Configuration COM = Communication Server CSV = Command Server DFA = Disk File Access DLK = Disk Lock DLM = Distributed Lock Management EVT = Cluster Management Event GMD = Group Membership Server GMS = Group Membership Service LOC = Local Communication LVM = Logical Volume Management MDV = Module Version MSG = Messaging NET = Network Management PKG = Package Management PLE = Placement Engine QSM = Quorum Service REM = Remote Communication RES = EMS Resources SDB = Status Database SEC = Security Service SES = Sessions SRV = Service Management STA = Status Database API SYN = Synchronization UNK = Unknown UTD = Utility Daemon
There is also debug logging of SG commands using the '-D' option (SG A.11.18 and later) If you want to change the logging for a single command, you can specify -D {1-5} or -O {filename) on the command line of any commands. These command line options will take precedence over the COMMAND_LOG_LEVEL/COMMAND_LOG_FILE values specified in /etc/cmcluster.conf.
