Logging Problems; Example - Some Nodes Are Missing - IBM RS/6000 SP Problem Determination Manual

This soft copy for use by IBM employees only.

2.5.5 Logging Problems

2.5.6 Example — Some Nodes Are Missing
This is an example of how to investigate if
example, assume node 8 is not showing up.
1. Run
−
Verify authorization through
•
If the logfile is no longer being updated:
Check the logging daemon:
−
splogd
Check that
The following example shows how you can check that
lssrc -s
using either the
# lssrc -a  grep splogd
splogd
#
# ps -eaf  grep splogd
root 15378 5854 0
-f /spdata/sys1/spmon/hwevents
root 18408 15248 0 11:22:43 pts/0 0:00 grep splogd
−
Check /etc/syslog.conf for daemon.notice entry
daemon.notice
−
Check that the /var/adm/SPlogs/SPdaemon.log exists with permissions
rw-r--r--.
−
Check that error record templates for SPMON exist:
# errpt -t | grep SPMON
• If the logging daemon dies:
−
Check for a core dump. If available, run
the core dump. If required, send the core dump and /unix file to the IBM
Support Center for investigation.
• If the hardware monitor daemon (hardmon) dies:
−
Check for a core dump. If available, run
the core dump. If required, send the core dump and /unix file to the IBM
Support Center for investigation.
−
Check /var/adm/SPlogs/spmon/hmlogfile.nnn.
splstdata -n
. This proves whether or not SDR has information about
this node.
klist
.
is running.
ps -eaf
or the command:
15378 active
May 08 - 0:00 /usr/lpp/ssp/bin/splogd
/var/adm/SPlogs/SPdaemon.log
spmon
Chapter 2. The Installation Process
splogd
is running
crash
to identify the reason for
crash
to identify the reason for
does not show a node. In this
37