beautypg.com

24 troubleshooting syslog-ng problems, 26 troubleshooting uninstallation problems – HP Insight Control Software for Linux User Manual

Page 242

background image

Corrective actions

Cause/Symptom

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

Use the telnet command to connect on the appropriate
port, port 2710 for Supermon and port 2709 for the mond

Supermon and mond are running, but there is no activity

Supermon listens on port 2710. The mond daemon listens
on port 2709.

daemon. Enter the S command after connection to see
metrics data output.

Perform the appropriate action:

Supermon and mon are running, but sensor data is not
reported

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

25.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:

The syslog-ng service does not appear to be running

# /etc/init.d/syslog-ng status

Run the logger command on the managed systems to
verify that the syslog-ng messages are logged:

The syslog-ng messages do not appear to be logged

# pdsh -a logger -p warn "msg"
# grep "msg"
/hptc_cluster/adm/logs/consolidated.log

Where msg is a specific message.

25.25 Troubleshooting Insight Control for Linux tool problems

Corrective action

Cause/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.26 Troubleshooting uninstallation problems

Corrective action

Cause/Symptom

Follow this procedure:

Possible hang might occur while running the uninstall.sh
script

The uninstall.sh script may hang while trying to
remove the HP SIM RPMs as the result of the

1.

On the CMS, run the ps command to find the process
ID of the hung mxinitconfig -r process.

# ps -ef | grep mxinitconfig
root 8626 8600 0 07:47 pts/0

mxinitconfig -r

command hanging; HP SIM must be

00:00:02 /opt/mx/bin/mxinitconfig -r

242 Troubleshooting