Installation guide

66 Chapter 3:Cluster Software Installation and Configuration
The importance of an event determines the severity level of the log entry. Important events should be
investigated before they affect cluster availability. The cluster can log messages with the following
severity levels, listed in order of severity level:
•
emerg — The cluster system is unusable.
•
alert — Action must be taken immediately to address the problem.
•
crit — A critical condition has occurred.
•
err — An error has occurred.
•
warning — A significant event that may require attention has occurred.
•
notice — An event that does not affect system operation has occurred.
•
info — An normal cluster operation has occurred.
•
debug — Diagnostic output detailing normal cluster operations.
The default logging severity levels for the cluster daemons are
warning and higher.
Examples of log file entries are as follows:
May 31 20:42:06 clu2 clusvcmgrd[992]: <info> Service Manager starting
May 31 20:42:06 clu2 clusvcmgrd[992]: <info> mount.ksh info: /dev/sda3 \
is not mounted
May 31 20:49:38 clu2 clulog[1294]: <notice> stop_service.ksh notice: \
Stopping service dbase_home
May 31 20:49:39 clu2 clusvcmgrd[1287]: <notice> Service Manager received \
a NODE_UP event for stor5
Jun 01 12:56:51 clu2 cluquorumd[1640]: <err> updateMyTimestamp: unable to \
update status block.
Jun 01 12:34:24 clu2 cluquorumd[1268]: <warning> Initiating cluster stop
Jun 01 12:34:24 clu2 cluquorumd[1268]: <warning> Completed cluster stop
Jul 27 15:28:40 clu2 cluquorumd[390]: <err> shoot_partner: successfully shot partner.
[1] [2] [3] [4] [5]
Each entry in the log file contains the following information:
• [1]Timestamp
• [2] Cluster system on which the event was logged
• [3] Subsystem that generated the event
• [4] Severity level of the event
• [5] Description of the event