Appendix C. Error And Event Logs - IBM eserver Cluster 1350 Installation And Service Manual

Appendix C. Error and event logs

There are multiple log files available to help monitor and troubleshoot the cluster:
Linux log
Node log
Cluster System Management log
Remote Supervisor Adapter log
American Power Conversion log
Linux Cluster Installation Tool event log
© Copyright IBM Corp. 2004
The Linux OS log can be viewed in /var/log/messages
The system logging daemons are syslogd and klogd. They are configured
via /etc/syslog.conf.
Log files are automatically rotated by the logrotate command. To rotation is
configured with the /etc/logrotate.conf file.
PC Doctor 2.0 is a ROM-based Diagnostic resident on the servers made
available by selecting F2 on boot up. PC Doctor error logs are in the
diagnostic portion of the boot up. Press F2 to run diagnostics, then F3 to
view log file.
POST/BIOS errors can be read by pressing F1 key during boot process and
then selecting View Error Logs from menu. This gives a POST code and
description of the error. For example:
301 Keyboard Input Error 164 Memory size has changed
Cluster System Management (CSM) log files can be viewed in the
/var/log/csm/installnode.log file.
Remote Supervisor Adapter (RSA) Adapter log files can be viewed by using
telnet into the adapter and selecting the View Log File from the menu.
You can view the American Power Conversion (APC) event log via Web,
FTP or local console I/F:
1. Telnet to the switch.
2. From main menu, you will see CTL-L for Event Log.
3. Events are logged in descending order by date, time and event.
You can view the Linux Cluster Installation Tool (LCIT) event log through a
local or remote console or terminal window:
1. Open a console window on the management node.
2. From the root directory, type: tail -f /var/log/messages.
77