PowerHA7.1 system mirror log 说明

最新推荐文章于 2021-04-15 21:05:00 发布

cuanxiu7017

最新推荐文章于 2021-04-15 21:05:00 发布

阅读量178

点赞数

Viewing PowerHA SystemMirror cluster log files

Your first approach to diagnosing a problem affecting your cluster should be to examine the cluster log files for messages output by the PowerHA? SystemMirror? subsystems. These messages provide valuable information for understanding the current state of the cluster. The following sections describe the types of messages output by the PowerHA SystemMirrorsoftware and the log files into which the system writes these messages.

For most troubleshooting, the /var/hacmp/log/hacmp.out file will be the most helpful log file. Resource group handling has been enhanced in recent releases and the hacmp.outfile has been expanded to capture more information on the activity and location of resource groups after cluster events. For instance, the hacmp.out file captures details of resource group parallel processing that other logs (such as the cluster history log) cannot report. The event summaries included in this log make it easier to see quickly what events have occurred recently in the cluster.

Reviewing cluster message log files
The PowerHA SystemMirror software writes the messages it generates to the system console and to several log files. Each log file contains a different subset of messages generated by the PowerHA SystemMirror software. When viewed as a group, the log files provide a detailed view of all cluster activity.
Understanding the cluster.log file
The /var/hacmp/adm/cluster.log file is a standard text file. When checking this file, first find the most recent error message associated with your problem. Then read back through the log file to the first message relating to that problem. Many error messages cascade from an initial error that usually indicates the problem source.
Understanding the hacmp.out log file
The /var/hacmp/log/hacmp.out file is a standard text file. The system cycles hacmp.out log file seven times. Each copy is identified by a number appended to the file name. The most recent log file is named /var/hacmp/log/hacmp.out; the oldest version of the file is named /var/hacmp/log/hacmp.out.7.
Viewing compiled hacmp.out event summaries
In the hacmp.out file, event summaries appear after those events that are initiated by the Cluster Manager. For example, node_up and node_up_complete and related subevents such as node_up_local and node_up_remote_complete.
Understanding the system error log
The PowerHA SystemMirror software logs messages to the system error log whenever a daemon generates a state message.
Understanding the cluster history log file
The cluster history log file is a standard text file with the system-assigned name /usr/es/sbin/cluster/history/cluster.mmddyyyy, where mm indicates the month, ddindicates the day in the month and yyyy indicates the year.
Collecting cluster log files for problem reporting
If you encounter a problem with PowerHA SystemMirror and report it to IBM? support, you may be asked to collect log files pertaining to the problem. In PowerHA SystemMirror, the Collect PowerHA SystemMirror Log Files for Problem Reporting SMIT panel aids in this process.
Managing cluster log files
PowerHA SystemMirror automatically manages cluster log files. The individual logs are limited to a maximum size and are removed after they reach a certain age, or are overwritten by newer versions.
Logging for clcomd
Logging for the clcomd daemon to clcomd.log and clcomddiag.log is turned on by default
The messages output from verification indicate where the error occurred (for example, the node, device, or command). The utility uses verbose logging to write to the /var/hacmp/clverify/clverify.log file.