Installation guide

134 Chapter 8:Cluster Administration
2. On the remaining cluster system, invoke the cluadmin utility and restore the cluster database.
To restore the database from the /etc/cluster.conf.bak file, specify the cluster re-
store command. To restore the database from a different file, specify the cluster re-
storefrom
file_name command.
The cluster will disable all running services, delete all the services, and then restore the database.
3. Restart the cluster software on the stopped system by invoking the cluster start command
located in the System V init directory. For example:
/sbin/service cluster start
4. Restart each cluster service by invoking the cluadmin utility on the cluster system on which you
want to run the service and specifying the service enable
service_name command.
8.6 Modifying Cluster Event Logging
It is possible to modify the severity level of the events that are logged by the clupowerd, cluquo-
rumd, cluhbd, and clusvcmgrd daemons. This is done so that the daemons on the cluster systems
will log messages at the same level.
To change a cluster daemon’s logging level on all the cluster systems, invoke the cluadmin utility,
and specify the cluster loglevel command, the name of the daemon, and the severity level.
Specify the severity level by using the name or the number that corresponds to the severity level. The
values 0 to 7 refer to the following severity levels:
0 — emerg
1 — alert
2 — crit
3 — err
4 — warning
5 — notice
6 — info
7 — debug
Note that the cluster logs messages with the designated severity level and also messages of a higher
severity. For example, if the severity level for quorum daemon messages is 2 (
crit), then the cluster
logs messages for crit, alert, and emerg severity levels. Note that setting the logging level to a low
severity level, such as 7 (
debug), will result in large log files over time.
The following example enables the cluquorumd daemon to log messages of all severity levels:
cluadmin
cluadmin> cluster loglevel cluquorumd 7
cluadmin>