HP Insight Control Software for Linux User Manual
Page 219
Corrective Actions
Cause/Symptom
2.
Restart the web server.
# /etc/init.d/httpd restart
For SLES operating systems:
1.
Create the symbolic link:
# ln -sf /opt/hptc/hpcgraph/hpcgraph.conf
/etc/apache2/conf.d/hpcgraph.conf
2.
Restart the web server.
For RHEL operating systems:
# /etc/init.d/apache2 stop
# /etc/init.d/apache2 startssl
For SLES operating systems:
# /etc/init.d/apache2 restart
Alternatively, remove the /etc/httpd/conf.d/
colplot-apache.conf
file and restart the web server.
Relaunch the Nagios web interface or restart the browser.
Blank page from HP Graph with Internet Explorer version
6.0
If you are using Internet Explorer Version 6.0, the initial
page with graphs is displayed when you select HP Graph.
When you select Show Detail Graphs and navigate to
another selection box, for example, systems, a blank page
is displayed and you cannot display any other Nagios
page.
The following table describes possible causes of problems with the Performance Dashboard tool
and provides actions to correct them.
Corrective Actions
Cause/Symptom
Perform the appropriate action:
Performance Dashboard initiates without data. It displays
all dark gray.
•
Restart the Performance Dashboard tool.
•
Determine if Nagios is collecting data.
The Performance Dashboard tool uses the same metric
gathering infrastructure as Nagios. If Performance
Dashboard is not working, check to see if Nagios is
successfully collecting data. If it is not, see
.
•
Use the following command to verify the infrastructure:
/opt/hptc/supermon/usr/bin/get_stats -n
CMS_IP_ADDR
Where CMS_IP_ADDR is the IP address of the CMS
•
Determine if there is any error output by running the
following command and interpreting its output:
# watch "ls -ltr /opt/hptc/cmu/tmp/GUI"
This command displays the following:
◦ a file named ReadSequence
◦ a series of log files named
number-ClusterResults.log
◦ a file named Sequence
Verify that these files are listed in this order and that the
number
s in the file names of the log files are sequential.
25.13 Troubleshooting monitoring problems
219