how parallel are host checks? (after service check fails)

[Marc Powell]

> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> admin at lists.sourceforge.net] On Behalf Of Juhani Tali
> Sent: Friday, August 12, 2005 7:43 AM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] how parallel are host checks? (after service
check
> fails)
> 
> 
> I have read something about that Nagios will stop processing all
service
> checks on all hosts if some host goes down, until the host check is
> finished.
> 
> Is this true? (also in 2.x?)
> 

Yes. In fact, _all_ other activities stop.
http://nagios.sourceforge.net/docs/1_0/checkscheduling.html - Host
Checks section. This behavior is maintained in 2.x. Nagios is primarily
a service monitor, not a host monitor.

> The problem is that I have about 400-500 hosts (cisco routers mostly)
> and I would like if a problem with one host would not delay locating
the
> problem on another host. Some, but not all host parents are defined.
> If it is true, that a host check freezes the entire nagios, then is
> there a way to make it more parallel?

Your host checks should be as simple as possible and finish as quickly
as possible. Running the checks in parallel defeats some of the other
functionality such as determining unreachable v.s. down hosts.

See 7 and 8 from http://nagios.sourceforge.net/docs/1_0/tuning.html

--
Marc


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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