HP Insight Control Software for Linux - Manual (Page 253)

In place of 192.0.2.1:60000, substitute the actual IP address of your CMS and the
repository web server port.
This entry automatically copies your master /etc/hosts file from the CMS as part of the
installation procedure.
23.23 Troubleshooting supermon problems
The following table describes possible causes of problems with Supermon and provides actions
to correct them.
Corrective actions Cause/Symptom
Perform the appropriate action:
• Ensure that the supermon service is running on the
CMS:
# service supermon status
If not, restart it:
# service supermon restart
• Ensure that the mond daemon is running on all the
managed systems:
# pdsh -a -x `headnode` /etc/init.d/mond
status
Supermon is not running
Use the telnet command to connect on the appropriate
port, port 2710 for Supermon and port 2709 for the mond
daemon. Enter the S command after connection; you
should see metrics data output. Supermon and mond are running, but there is no activity
Supermon listens on port 2710. The mond daemon listens
on port 2709.
Perform the appropriate action:
• Ensure that sensor data is collected and stored in RRD:
# shownode metrics sensors
• Verify that metric gathering is working correctly:
# cd /opt/hptc/supermon/usr/bin
# ./get_stats -n server -c nodeinfo
# ./get_stats -n server -c sensors
Supermon and mon are running, but sensor data is not
reported
23.24 Troubleshooting syslog-ng problems
The following table describes possible causes of problems with syslog-ng and provides actions
to correct them.
Corrective actions Cause/Symptom
Verify that syslog-ng is running:
# /etc/init.d/syslog-ng status
The syslog-ng service does not appear to be running
Run the logger command on the managed systems to
verify that the syslog-ng messages are logged:
# pdsh -a logger -p warn "msg"
# grep "msg"
/hptc_cluster/adm/logs/consolidated.log
Where msg is a specific message.
The syslog-ng messages do not appear to be logged
23.23 Troubleshooting supermon problems 253