Installation guide

Note that this command resets all other properties that you can set with the --setcman option to their
default values, as described in Section 5.1.5, “ Commands that Overwrite Previous Settings” .
When you use the ccs --setcman command to add, remove, or modify the two _no d e option, you
must restart the cluster for this change to take effect. For information on starting and stopping a
cluster with the ccs command, refer to Section 6.2, “ Starting and Stopping a Cluster”.
5.14 .4 . Logging
You can enable debugging for all daemons in a cluster, or you can enable logging for specific
cluster processing.
To enable debugging for all daemons, execute the following command. By default, logging is
directed to the /var/lo g /cl uster/daemon. l o g file.
ccs -h host --setlogging [logging options]
For example, the following command enables debugging for all daemons.
# ccs -h no d e1. example. co m --setlo g g i ng d ebug = o n
Note that this command resets all other properties that you can set with the --setl o g g i ng option
to their default values, as described in Section 5.1.5, “ Commands that Overwrite Previous Settings” .
To enable debugging for an individual cluster process, execute the following command. Per-daemon
logging configuration overrides the global settings.
ccs -h host --addlogging [logging daemon options]
For example, the following commands enable debugging for the coro sync and fenced daemons.
# ccs -h no d e1. example. co m --ad d l o g g i ng name=co ro sync debug = o n
# ccs -h no d e1. example. co m --ad d l o g g i ng name=fenced d ebug = o n
To remove the log settings for individual daemons, use the following command.
ccs -h host --rmlogging name=clusterprocess
For example, the following command removes the daemon-specific log settings for the fenced
daemaon
ccs -h host --rmlogging name=fenced
For a list of the logging daemons for which you can enable logging as well as the additional logging
options you can configure for both global and per-daemon logging, refer to the cluster. co nf(5)
man page.
Note that when you have finished configuring all of the components of your cluster, you will need to
sync the cluster configuration file to all of the nodes, as described in Section 5.15, “ Propagating the
Configuration File to the Cluster Nodes” .
5.14 .5. Configuring Redundant Ring Prot ocol
⁠Chapt er 5. Configuring Red Hat Hig h Availabilit y Add- O n Wit h t he ccs Command
99