HP-UX HB v13.00 Ch-15 - Serviceguard

HP-UX Handbook – Rev 13.00 Page 51 (of 108)
Chapter 15 Serviceguard
October 29, 2013
Serviceguard Logs
 Serviceguard daemons log their actions to /var/adm/syslog/syslog.log. If nothing is found
in this file, check if syslogd still works as expected (‘logger testing syslogd’).
 Package start and stop actions are logged in the package log which is typically located in
the package directory or the /var/adm/cmcluster/logs/ (modular packages). Modular
packages offer the script_log_file parameter to identify a different path/file.
 Unless DSAU is configured (see next item), it may be necessary to inspect all system’s
syslog.log and/or package logs to understand the actual events preceding a problem.
 If Distributed Systems Administration Utilities (DSAU) is configured to consolidate
system logs, the syslogs may be located on another system. Otherwise, cluster level
events are saved locally in the normal location.
 DSAU offers following functions: Configuration synchronization, Log consolidation,
Command fan-out
 With consolidated logging, you can examine a single log that contains entries from all
systems (e.g. Cluster Nodes) in your configuration.
For more details please check out the document: Managing Systems and Workgroups (A Guide
for HP-UX System administrators, http://docs.hp.com -> choose OS -> Choose System
Administration). Link as in July 2007: http://www.docs.hp.com/en/B2355-90950/B2355-
90950.pdf.
Debug logging
Package debug logging
Package start/stop issues are captured in the package log. Legacy packages log their operations
to a log file in the same directory as the package control script. Modular packages have a
parameter that allows the admin to identify the destination of the package log. Typically, it will
be either the package directory or /var/adm/cmcluster/logs/.
Modular packages have adjustable log levels:
Level 0 : user visible informative messages
Level 1 : slightly more detail user visible informative messages
Level 2 : messages provide logic flow
Level 3 : messages provide detailed data structure information
Level 4 : debugging information that provides detailed data
Level 5 : function call flow
To change the log level, edit the package configuration file and set the log_level parameter, then run
cmapplyconf on the file, then start/stop the package and check the package log.
Legacy package control scripts do not offer a log_level feature, so if the package log does not contain
sufficient detail, insert a ‘set –x’ near the top of the package control script, and test the package startup
or shutdown to capture specific actions in the package log to identify package run/halt failures. (No
cmapplyconf is necessary).
Cluster-level logging