HP Insight Control for Linux 6.2 User Guide

25.23 Troubleshooting Supermon problems
The following table describes possible causes of problems with Supermon and provides actions
to correct them.
Corrective actionsCause/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 to 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
25.24 Troubleshooting syslog-ng problems
The following table describes possible causes of problems with syslog-ng and provides actions
to correct them.
Corrective actionsCause/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
25.25 Troubleshooting Insight Control for Linux tool problems
Corrective actionCause/Symptom
Select only target managed systems with a system type
of Server.
"Tool Launch OK?" says NO
Insight Control for Linux tools only work with systems
with a system type of Server.
25.23 Troubleshooting Supermon problems 257