IBM RS/6000 SP Problem Determination Manual page 218

Problems with System Monitor GUI
Hardware monitor daemon (hardmon) is not running
Logging problems
198
SP PD Guide
• spmon
command fails to start the System Monitor GUI. Then check the
following:
−
Verify authorization
klist
- Run command to verify that kerberos tickets have not expired.
Important
spmon
will not run if kerberos tickets never expire.
kinit
- Re-issue
- Check the /spdata/sys1/spmon/hmacls file to ensure that the
kerberos principal name and instance for your ID is in this hardware
monitor ACL file.
sp2cw0 root.admin a
sp2cw0 hardmon.sp2cw0 a
1 root.admin vsm
1 hardmon.sp2cw0 vsm
−
Ensure you have exported the DISPLAY variable:
# echo $DISPLAY
<hoatname or IP address>:0
•
If the open session failure message window is displayed after opening the
System Monitor GUI, then verify authorization using
authorization using the
/spdata/sys1/spmon/hmacls file.
•
Execute the following command to verify that the hardmon daemon is
functioning correctly:
# hmmon -Q 1:1
• If the above command does not work, check the hardmon log file at
/var/adm/SPlogs/spmon/hmlogfile.xxx, where xxx is the creation date.
•
Logfile is no longer being updated
Check the logging daemon
−
Check that splogd is running
The following example shows how you can check that the splogd is
running:
# lssrc -a  grep splogd
splogd
or,
# 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
This soft copy for use by IBM employees only.
command, if required.
kinit
command. If the problem persists, check the
15378
May 08 - 0:00 /usr/lpp/ssp/bin/splogd
klist
and request
active