Host check clarification

Israel Brewster israel at frontierflying.com
Tue Jan 15 01:54:36 CET 2008




On Jan 14, 2008, at 1:27 PM, Sloane, Robert Raymond wrote:

> To start off with, there isn't any WARNING state for hosts, just UP,
> DOWN, PENDING or UNREACHABLE.  Assume the host is OK to start off  
> with.
> If the host check returns DOWN then then the parent of the host will  
> be
> check to see if it is DOWN.  If the parent is OK, then the host is
> marked as DOWN in a soft state, and if the parent is DOWN, then the  
> host
> is UNREACHABLE. The host check will be repeated in rapid succession
> until the host is either UP or the retry count is reached.  If any  
> check
> returns the host as UP, then Nagios marks the host UP and goes to the
> next thing.  If the retry count is reached, then the host is marked as
> DOWN in a hard state and the notification process is started.
>
> Does that help?

Yep, that answers it. Thanks!


-----------------------------------------------
Israel Brewster
Computer Support Technician
Frontier Flying Service Inc.
5245 Airport Industrial Rd
Fairbanks, AK 99709
(907) 450-7250 x293
-----------------------------------------------
>
> -- 
> Bob Sloane, University of Kansas Computer Center, Lawrence, KS, 66045
> Email:sloane at ku.edu http://www.ku.edu/home/sloane Phone:(785)864-0444
>
>
>> -----Original Message-----
>> From: nagios-users-bounces at lists.sourceforge.net
>> [mailto:nagios-users-bounces at lists.sourceforge.net] On Behalf
>> Of Israel Brewster
>> Sent: Monday, January 14, 2008 4:18 PM
>> To: Nagios Users mailinglist
>> Subject: [Nagios-users] Host check clarification
>>
>>
>> I need some clarification as to how exactly the host check
>> determines
>> if a host is down. In the default configuration, the
>> check-host-alive
>> command sends a single ping, which can be considered (obviously)
>> either ok, warning, or critical. The host then has a
>> max_check_attempts setting of three, which if I understand things
>> correctly means it will try this check twice more, in rapid
>> succession, before putting the host into a hard state. My
>> question is
>> what is the logic if one of these three checks returns a different
>> state than the other two? Say, for example, the first ping
>> never makes
>> it back, therefore returning a critical state, but the second and
>> third come back, giving OK states? is the host then considered up or
>> down? Thanks!
>>
>> -----------------------------------------------
>> Israel Brewster
>> Computer Support Technician
>> Frontier Flying Service Inc.
>> 5245 Airport Industrial Rd
>> Fairbanks, AK 99709
>> (907) 450-7250 x293
>> -----------------------------------------------
>>
>>
>>
>> --------------------------------------------------------------
>> -----------
>> Check out the new SourceForge.net Marketplace.
>> It's the best place to buy or sell services for
>> just about anything Open Source.
>> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.n
> et/marketplace
> _______________________________________________
> 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


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
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





More information about the Users mailing list