Table of Contents
Advertisement
Section 8.12:Diagnosing and Correcting Problems in a Cluster
/sbin/cluconfig --init=/dev/raw/raw1
6. Start the cluster daemons by invoking the cluster start command located in the System V
init directory on both cluster systems. For example:
/sbin/service cluster start
8.11 Disabling the Cluster Software
It may become necessary to temporarily disable the cluster software on a member system. For exam-
ple, if a cluster system experiences a hardware failure, an administrator may want to reboot the system,
but prevent it from rejoining the cluster in order to perform maintenance on the system.
Use the /sbin/chkconfig utility to be able to boot a cluster system, without allowing it to rejoin
the cluster. For example:
/sbin/chkconfig --del cluster
When you want the system to rejoin the cluster, use the following command:
/sbin/chkconfig --add cluster
You can then reboot the system or run the cluster start command located in the System V init
directory. For example:
/sbin/service cluster start
8.12 Diagnosing and Correcting Problems in a
Cluster
To ensure the proper diagnosis of any problems in a cluster, event logging must be enabled. In addition,
if problems arise in a cluster, be sure to set the severity level to
will log descriptive messages that may help solve problems. Once any issues have been resolved, reset
the debug level back down to its default value of
being generated.
If problems occur while running the cluadmin utility (for example, problems enabling a service),
set the severity level for the clusvcmgrd daemon to
be displayed while running the cluadmin utility. See Section 8.6, Modifying Cluster Event Logging
for more information.
Use Table 8–5, Diagnosing and Correcting Problems in a Cluster to troubleshoot issues in a cluster.
debug
to avoid excessively large log message files from
info
. This will cause debugging messages to
debug
for the cluster daemons. This
137
Advertisement
Table of Contents
