Linux FailSafe maintains system logs for each of the Linux FailSafe daemons. You can customize the system logs according to the level of logging you wish to maintain.
A log group is a set of processes that log to the same log file according to the same logging configuration. All Linux FailSafe daemons make one log group each. Linux FailSafe maintains the following log groups:
Commands log
Cluster reset services (crsd) log
Diagnostics log
HA monitoring agents (ha_ifmx2) log
Cluster membership daemon (ha_cmsd) log
Linux FailSafe daemon (ha_fsd) log
Group communication daemon (ha_gcd) log
network interface monitoring daemon (ha_ifd) log
Action and Failover policy scripts log
System resource manager (ha_srmd) log
Log group configuration information is maintained for all nodes in the pool for the cli and crsd log groups or for all nodes in the cluster for all other log groups.You can also customize the log group configuration for a specific node in the cluster or pool.
When you configure a log group, you specify the following information:
The log level, specified as character strings with the CUI and numerically (1 to 19) with the CLI, as described below
The log file to log to
The node whose specified log group you are customizing (optional)
The log level specifies the verbosity of the logging, controlling the amount of log messages that Linux FailSafe will write into an associated log group's file. There are 10 debug level. Table 5-1, shows the logging levels as you specify them with the GUI and the CLI.
Table 5-1. Log Levels
GUI level | CLI level | Meaning |
|---|---|---|
Off | 0 | No logging |
Minimal | 1 | Logs notification of critical errors and normal operation |
Info | 2 | Logs minimal notification plus warning |
Default | 5 | Logs all Info messages plus additional notifications |
Debug0 | 10 | |
... | Debug0 through Debug9 (11 -19 in CLI) log increasingly more debug information, including data structures. Many megabytes of disk space can be consumed on the server when debug levels are used in a log configuration. | |
Debug9 | 19 |
Note: Notifications of critical errors and normal operations are always sent to /var/log/failsafe/. Changes you make to the log level for a log group do not affect SYSLOG.
The Linux FailSafe software appends the node name to the name of the log file you specify. For example, when you specify the log file name for a log group as /var/log/failsafe/cli, the file name will be /var/log/failsafe/cli_nodename.
The default log file names are as follows.
log file for cluster membership services daemon in node nodename
log file for group communication daemon in node nodename
log file for system resource manager daemon in node nodename
log file for Linux FailSafe daemon, a policy implementor for resource groups, in node nodename
log file for monitoring agent named agent in node nodename. For example, ifd_nodename is the log file for the interface daemon monitoring agent that monitors interfaces and IP addresses and performs local failover of IP addresses.
log file for reset daemon in node nodename
log file for scripts in node nodename
log file or internal administrative commands in node nodename invoked by the Cluster Manager GUI and Cluster Manager CLI
For information on using log groups in system recovery, see Chapter 9.
To configure a log group with the Cluster Manager GUI, perform the following steps:
Launch the FailSafe Manager.
On the left side of the display, click on the “Nodes & Clusters” category.
On the right side of the display click on the “Set Log Configuration” task link to launch the task.
Enter the selected inputs.
Click on “OK” at the bottom of the screen to complete the task.
You can configure a log group with the following CLI command:
cmgr> define log_group A [on node B] [in cluster C] |
You specify the node if you wish to customize the log group configuration for a specific node only. If you have specified a default cluster, you do not have to specify a cluster in this command; Linux FailSafe will use the default.
The following prompt appears:
Enter commands, when finished enter either "done" or "cancel" log_group A? |
When this prompt of the node name appears, you enter the log group parameters you wish to modify in the following format:
log_group A? set log_level to A log_group A? add log_file A log_group A? remove log_file A |
When you are finished configuring the log group, enter done to return to the cmgr prompt.
Use the following CLI command to modify a log group:
cmgr> modify log_group A on [node B] [in cluster C] |
You modify a log group using the same commands you use to define a log group.
To display log group definitions with the Cluster Manager GUI, run “Set Log Configuration” and choose the log group to display from the rollover menu. The current log level and log file for that log group will be displayed in the task window, where you can change those settings if you desire.
Use the following command to view the parameters of a defined resource:
cmgr> show log_groups |
This command shows all of the log groups currently defined, with the log group name, the logging levels and the log files.
For information on viewing the contents of the log file, see Chapter 9.