HP Insight Control for Linux 6.0 User Guide

• If the output reports that vars.ini have been resynchronized for a managed system,
verify that there is a self-signed certificate for the Apache service and that that service is
running. For troubleshooting information on the Apache service, see Section 23.3 (page 216).
23.14.7 Nagios gather_all_data script reports check_nrpe errors
These errors include socket timeouts and refused connections. The nrpe daemon is unable to
configure the server because the check_nagios_vars script is unable to write vars.ini to
the server.
Use the ping command, specifying the server by name; it returns its IP address. Compare that
IP address to the IP address that HP SIM reports for that server. They must match.
23.14.8 Troubleshooting Nagios problems
The following table describes possible causes of problems related to Nagios and provides actions
to correct them.
Corrective ActionsCause/Symptom
If Nagios fails to start, one or more Nagios daemons failed
to start on the CMS. To start the Nagios daemons
manually to overcome this, follow these steps:
1. Log in to the CMS as the root user.
2. Stop the Nagios service:
# /etc/init.d/nagios stop
3. Change to the following directory:
# cd /opt/hptc/nagios/bin
4. Start the Nagios service:
# ./nagios -v ../etc/nagios_local.cfg
Nagios fails to start
Restart the Apache service on the CMS:
Log into the CMS as root and use the following commands
for RHEL:
# /etc/init.d/httpd stop
# /etc/init.d/httpd start
Log into the CMS as root and use the following commands
for SLES:
# /etc/init.d/apache2 stop
# /etc/init.d/apache2 startssl
Nagios startup error: Can't find
/nagios/cgi-bin/status.cgi.
Verify that the php RPM along with its required
dependencies are on your CMS.
To verify on a RHEL CMS:
# rpm -qa | grep php
To verify on a SLES CMS:
# rpm -qa | grep php5
If the php RPM and its required dependencies are not
installed, use the rpm command to install them.
Nagios startup error: The browser displays a directory
list of Nagios files instead of the Nagios main window.
240 Troubleshooting