Active host check scheduling in a distributed environment

[Paul Corcoran]

HI,

I run a distributed Nagios environment consisting of 1 parent server and 2
child servers.

The child servers perform all the service checking while the parent server
should be performing active service checks.

The host definitions are configured to perform host checks every 5 minutes.
The retry interval is 1 minute and the max attempts is set to 5.

We are monitoring 580 hosts and approx 4000 services.

I noticed when a host down was detected the parent server did not perform
any retries of the host. This led to the status of the host being stuck in a
SOFT state and therefore no alerts were sent out as required. I noticed that
the child server performed the host checks without any problem and the host
was logged as being in a HARD down state after 5 failed attempts.

Is there a specific variable in nagios.cfg that explicitly tells the server
to perform active checks?

Is it best practice to have the 2 child servers perform passive host checks?
Is it possible that processing all the passive service check info is causing
the parent server to lag behind in it's own process queue?

Thanks for you help.

Paul
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20090714/7bd62cd8/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time, 
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null