The HACMP 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 HACMP software.When viewed as a group, the log filesprovide a detailed view of all cluster activity.
Although the actual location of the log files on the system may seem scattered, the log diversity provides information for virtually any HACMP event.Moreover, you can customize the location of the log files, and specify the verbosity of the logging operations.
The following list describes the log files into which the HACMP software writes messages and the types of cluster messages they contain.The list also provides recommendations for using the different log files.
/usr/es/adm/cluster.log
Contains time-stamped, formatted messages generated
by HACMP scripts and daemons.
/tmp/hacmp.out
Contains time-stamped, formatted messages generated
by HACMP scripts on the current day. In verbose mode
(recommended), this log file contains a line-by-line record
of every command executed by the scripts, including the
values of all arguments to each command. An event
summary of each high-level event is included at the end of
each event’s details (similar to adding the -x option to a
shell script).
system error log
Contains time-stamped, formatted messages from all AIX
subsystems, including scripts and daemons.
/usr/es/sbin/cluster/history/cluster.mmddyyyy
Contains time-stamped, formatted messages generated
by HACMP scripts. The system creates a cluster history
file every day, identifying each file by its file name
extension, where mm indicates the month, dd indicates
the day, and yyyy the year.
/tmp/clstrmgr.debug
Contains time-stamped, formatted messages generated
by clstrmgrES activity. The messages are verbose. With
debugging turned on, this file grows quickly. You should
clean up the file and turn off the debug options as soon as
possible.
/tmp/cspoc.log
Contains time-stamped, formatted messages generated
by HACMP C-SPOC commands. The file resides on the
node that invokes the C-SPOC command.
/tmp/dms_loads.out
Stores log messages every time HACMP triggers the
deadman switch.
/tmp/emuhacmp.out
Contains time-stamped, formatted messages generated
by the HACMP Event Emulator. The messages are
collected from output files on each node of the cluster,
and cataloged together into the /tmp/emuhacmp.out log
file.
/var/hacmp/clverify/clverify.log
The file contains the verbose messages output by the
clverify utility. The messages indicate the node(s),
devices, command, and so on, in which any verification
error occurred.
/var/ha/log/grpsvcs, /var/ha/log/topsvcs, and /var/ha/log/grpglsm
Contains time-stamped messages in ASCII format. All
these files track the execution of the internal activities of
their respective daemons.
Although the actual location of the log files on the system may seem scattered, the log diversity provides information for virtually any HACMP event.Moreover, you can customize the location of the log files, and specify the verbosity of the logging operations.
The following list describes the log files into which the HACMP software writes messages and the types of cluster messages they contain.The list also provides recommendations for using the different log files.
/usr/es/adm/cluster.log
Contains time-stamped, formatted messages generated
by HACMP scripts and daemons.
/tmp/hacmp.out
Contains time-stamped, formatted messages generated
by HACMP scripts on the current day. In verbose mode
(recommended), this log file contains a line-by-line record
of every command executed by the scripts, including the
values of all arguments to each command. An event
summary of each high-level event is included at the end of
each event’s details (similar to adding the -x option to a
shell script).
system error log
Contains time-stamped, formatted messages from all AIX
subsystems, including scripts and daemons.
/usr/es/sbin/cluster/history/cluster.mmddyyyy
Contains time-stamped, formatted messages generated
by HACMP scripts. The system creates a cluster history
file every day, identifying each file by its file name
extension, where mm indicates the month, dd indicates
the day, and yyyy the year.
/tmp/clstrmgr.debug
Contains time-stamped, formatted messages generated
by clstrmgrES activity. The messages are verbose. With
debugging turned on, this file grows quickly. You should
clean up the file and turn off the debug options as soon as
possible.
/tmp/cspoc.log
Contains time-stamped, formatted messages generated
by HACMP C-SPOC commands. The file resides on the
node that invokes the C-SPOC command.
/tmp/dms_loads.out
Stores log messages every time HACMP triggers the
deadman switch.
/tmp/emuhacmp.out
Contains time-stamped, formatted messages generated
by the HACMP Event Emulator. The messages are
collected from output files on each node of the cluster,
and cataloged together into the /tmp/emuhacmp.out log
file.
/var/hacmp/clverify/clverify.log
The file contains the verbose messages output by the
clverify utility. The messages indicate the node(s),
devices, command, and so on, in which any verification
error occurred.
/var/ha/log/grpsvcs, /var/ha/log/topsvcs, and /var/ha/log/grpglsm
Contains time-stamped messages in ASCII format. All
these files track the execution of the internal activities of
their respective daemons.
1 comment:
very helpfull for me
Post a Comment