Software for Linux Owner's manual

Corrective ActionsCause/Symptom
Run the following commands to resynchronize the
vars.ini file across all managed systems:
Nagios “Management Settings Monitor” service reports
vars warning
# cd /opt/hptc/nagios/libexec
# ./check_nagios_vars --update
Remove the nagios_vars.db file:Nagios services report a non-OK status
Under very rare circumstances, the Nagios cache might
become unsynchronized. If this occurs, it is possible that
some Nagios services do not operate correctly.
# rm /opt/hptc/nagios/etc/nagios_vars.db
Ensure that all Nagios services associated with the
managed systems have:
Nagios services report WARNING status because "data is
stale"
Active Checks set to DISABLED
Passive Checks set to ENABLED
All passive services should have a red "p" next to the
service name.
The following monitor services are the only active services;
they reside on the CMS (nh) only:
Apache HTTPS Server
Configuration Montor
IP Assignment - DHCP
Management Settings Monitor
Nagios Monitor
Sensor Collection Monitor
Supermon Metrics Monitor
Switch Data Collection
Syslog Alert Monitor
Systems Event Log Monitor
IMPORTANT: This is the default configuration required
by Insight Control for Linux; this configuration is set after
running the OptionsIC-LinuxConfigure Management
Services task. Do not alter these settings from the default
configuration.
Run the following commands to restart mond on all
managed systems:
Nagios services might report warning
Nagios services might report WARNING - No sensor
data is available or Data is stale.
# pdsh -w `shownode servers nagios_monitor`
/etc/init.d/supermon restart
# pdsh -a -x `shownode servers
nagios_monitor` /etc/init.d/mond restart
Use the following procedure to update the default
thresholds in the /opt/hptc/nagios/etc/
Nagios generates CRITICAL or WARNING Alerts for the
Nodeinfo service
The Nagios default threshold values for total
processes, user processes, and zombie
nagios_vars.ini file. HP recommends saving a copy
of the original file before making any updates.
1. Save a copy of the original file:
# cp /opt/hptc/nagios/etc/nagios_vars.ini
/opt/hptc/nagios/etc/nagios_vars.ini.orig
processes might be too small for certain system
configurations, particularly those with virtualization
operating systems. If so, you will encounter CRITICAL or
WARNING alerts for the NodeInfo service.
2. Edit the nagios_vars.ini file to update the values
for the *_procs_warning and *_procs_critical
parameters to values that apply to your environment.
For example:
[default]
total_procs_warning = 400
total_procs_critical = 500
user_procs_warning = 200
25.14 Nagios Troubleshooting 227