IBM RS/6000 SP, Problem Determination Manual

Page: 57 / 316

This soft copy for use by IBM employees only.
−
Verify authorization through
klist
.
2.5.5 Logging Problems
•
If the logfile is no longer being updated:
Check the logging daemon:
−
Check that
splogd
is running.
The following example shows how you can check that
splogd
is running
using either the
lssrc -s
or the
ps -eaf
command:
# lssrc -a

grep splogd
splogd 15378 active
#
# ps -eaf

grep splogd
root 15378 5854 0 May 08 - 0:00 /usr/lpp/ssp/bin/splogd
-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 /var/adm/SPlogs/SPdaemon.log
−
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
crash
to identify the reason for
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
crash
to identify the reason for
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.
2.5.6 Example — Some Nodes Are Missing
This is an example of how to investigate if spmon does not show a node. In this
example, assume node 8 is not showing up.
1. Run splstdata -n . This proves whether or not SDR has information about
this node.
Chapter 2. The Installation Process
37