host checking logic

[Marc Powell]

> -----Original Message-----
> From: Terry [mailto:td3201 at gmail.com]
> Sent: Thursday, October 11, 2007 12:55 PM
> To: Marc Powell
> Cc: Nagios Users mailinglist
> Subject: Re: [Nagios-users] host checking logic
> 
> On 10/11/07, Marc Powell <marc at ena.com> wrote:
> >
> >
> > > -----Original Message-----
> > > From: nagios-users-bounces at lists.sourceforge.net
[mailto:nagios-users-
> > > bounces at lists.sourceforge.net] On Behalf Of Terry
> > > Sent: Thursday, October 11, 2007 10:54 AM
> > > To: Nagios Users mailinglist
> > > Subject: [Nagios-users] host checking logic
> > >
> > > Hello,
> > >
> > > I have a host that will not be reachable via icmp
(check-host-alive).
> > > However, it will have services that are, check_tcp for example.
> >
> >
> > > I always assumed (ya, i know) that nagios assumed the host was up
if
> > > it had services that were OK.  Obviously I am wrong or have
something
> > > misconfigured.  How can I get around this issue?
> >
> > It will assume the host is up if the very first check of a service
on
> > that host is successful. After that, there are no further
assumptions.


> 
> Thanks for your reply.  Why is nagios even checking it given the
> configuration: ?
> 
> check_interval=0
> check_host_freshness=0

Nagios will always run host checks as needed unless you specifically
tell it not to by setting check_period to none or removing the host's
check_command entirely. These are called on-demand checks and are
different than active and passive checks.

http://nagios.sourceforge.net/docs/2_0/checkscheduling.html#host_checks

The first option controls whether nagios periodically checks the state
of a host regardless of the state of services on that host (an active
check). You normally don't need that nor do you normally want to enable
it. Your current setting is appropriate.

The second option controls whether nagios periodically checks whether
there has been a 'recent' check result submitted for this host
(unrelated to any services on that host). This is almost always
associated with passive host check submissions and requires
check_freshness to be enabled in the host definition and for you to be
submitting passive host check results. You have not indicated that you
are using passive host checks and I would expect that you would be very
aware of that if you were. As such, this setting has no impact/value for
you.

--
Marc

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
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