Increase Ping timeout to 60 sec

[gselvakumar]

Hi Team,
I have increased the ping timeout value to 60 secs but in the portal it is still showing old timeout value.The host uses the xiwizard_switch_host template which uses command check_xi_host_ping.I had changed the timeout value as mentioned below

Code: Select all

 $USER1$/check_icmp -H $HOSTADDRESS$ -w $ARG1$,$ARG2$ -c $ARG3$,$ARG4$ -p 5 -t 60

Could please help me.

[rkennedy]

Please post or PM over your /usr/local/nagios/var/objects.cache file for us to look at, this should help identify what's going on.

[gselvakumar]

Hi rkennedy,

PFA of /usr/local/nagios/var/objects.cache file

[tgriep]

That timeout is the global host timeout setting in the /usr/local/nagios/etc/nagios.cfg file.
So if you edit that file and change the following from

Code: Select all

host_check_timeout=30

to

Code: Select all

host_check_timeout=60

Then restart nagios by running the following while logged in as root to the server

Code: Select all

service nagios restart

That will increase that timeout setting for you.

[gselvakumar]

Hi tgriep,

I edited the host timeout setting in the /usr/local/nagios/etc/nagios.cfg file
from

Code: Select all

host_check_timeout=30

to

Code: Select all

host_check_timeout=60

and restarted the nagios agent.But it is still showing old time out value.

[bwallace]

Did you restart the Nagios server (you mentioned "agent") after making those changes?
Restarting/reloading is necessary when you modify your configuration files and want those changes to take effect.

service nagios restart

Some other methods for restarting:
Restart via Init Script: The easiest way to restart the Nagios daemon is by using the init script like so:
/etc/rc.d/init.d/nagios reload

Restart via Web Interface: You can restart the Nagios through the web interface by clicking the "Process Info" navigation link and selecting "Restart the Nagios process":

Restart manually: You can restart the Nagios process by sending it a SIGHUP signal like so:
kill -HUP <nagios_pid>


If issue persists, then check for multiple Nagios processes running as this will cause an array of problems.

run this cmd on your nagios server:
ps - aef | grep nagios.cfg

* Look for multiple parent (PPID) processes. The Nagios process forks itself to run checks therefore subprocesses are normal. The nagios user should probably be the only owner of the nagios process. If in any doubt post the output here.

If there are multiple Nagios processes running, run these commands to resolve:

service nagios stop
killall -9 nagios
service nagios start