IBM RS/6000 SP, Руководство по определению проблем

Страница: 56 / 316

This soft copy for use by IBM employees only.
2.5.4 Problems with System Monitor GUI
•
If the
spmon
command fails to start the System Monitor GUI, you need to
check the following:
−
Verify authorization:
- Run the klist command to verify that the kerberos tickets are not
expired.
- Reissue the kinit command if required.
- Check /spdata/sys1/spmon/hmacls 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 DISPLAY:
# echo $DISPLAY
9.12.0.3:0
In this example, DISPLAY is exported correctly to the local display on the
PC with an IP address 9.12.0.3.
•
If an open session failure message window is displayed after opening the
System Monitor GUI, you need to check following:
−
Verify authorization using
klist
, request authorization using
kinit
, and
check /spdata/sys1/spmon/hmacls.
−
Check hardware monitor daemon (hardmon):
- Issue the hardware monitor command using an ID that has monitor
authority and a valid ticket-granting ticket from
kinit
.
Following is an example command to check frame 1, node 1:
# hmmon -Q 1:1
If this command does not work, check the hardmon log
/var/adm/SPlogs/spmon/hmlogfile, where nnn is the Julian date of
when the file was created.
- Check /var/adm/SPLogs/spmon/hmlogfile.nnn
•
If the System Monitor GUI hangs, it could be because of performance
reasons or authorization problems. Check the following:
−
Check performance:
- Check for adequate paging space.
- Check overall CPU utilization.
- Check CPU utilization of hardmon and splogd:
# ps vgc | grep hardmon
# ps vgc | grep splogd
If the CPU utilization rate is very high and cannot be attributed to the
hardmon or logging daemon, then look for other processes which are
consuming the CPU resources. Contact the IBM Support Center if
you cannot resolve the problem.
36
SP PD Guide