Help rephrasing my question

[Tedman Eng]

I would guess that it's possibly related to state changes.  I think the
classification of down vs. unreachable only happens upon state changes.
States can be OK (up) or non-OK (down or unreachable)

The child host (down) is in a non-OK state.  When its parent goes into
non-OK (down) , the child was already non-OK (down), therefore doesn't
reclassify to a different non-OK (unreachable).

I would agreee that it seems more logical to that only the topmost branch
during an outage should be considered Down, and all child nodes to be
considered Unreachable.


> -----Original Message-----
> From: Morris, Patrick [mailto:patrick.morris at hp.com]
> Sent: Friday, August 11, 2006 4:33 PM
> To: Brian McKee; Nagios-users at lists.sourceforge.net
> Subject: Re: [Nagios-users] Help rephrasing my question
> 
> 
> >   I posted a query on this list a week ago which no-one 
> responded to.
> > https://sourceforge.net/mailarchive/forum.php?thread_id=295006
> > 09&forum_id=1873
> > 
> >   That was  a rephrased form of a question I asked a few 
> > weeks earlier than that
> > https://sourceforge.net/mailarchive/forum.php?thread_id=255356
> > 73&forum_id=1873
> > 
> > I'd appreciate if anyone has a minute to review those 
> > questions and suggest how I might either determine a 
> > resolution on my own, or rephase the issue such that someone 
> > here can contribute a solution.
> > 
> > I did think at the time that I provided enough information, 
> and I have
> > attempted to resolve the issue on my own.    I have read 
> (among other
> > documents) 
> > http://www.nagios.org/faqs/viewfaq.php?faq_id=14&expand=false&
> > showdesc=false
> > and believe I understand it.
> > 
> > Responses off list or on as you feel appropriate.
> 
> So, just to keep anyone reading this on the same page, the question
> seems to be something like "why does a host state not change from down
> to unreachable when a parent node later goes down?"
> 
> I'm not sure I can anwer it, other than to give reasons why I think it
> works the way it does.  When a host goes down, its parent nodes are
> checked.  If they're OK, the host is marked down until it 
> comes back up.
> If not, it's marked unreachable until the parent node comes back up.
> 
> I would guess the behavior you're seeing is because Nagios is waiting
> for the host to come up, and it's not taking *every* state change into
> account.  This may be a bug, and it may be a feature, but it's
> apparently the way it works based on your observations (which 
> I haven't
> attempted to verify).
> 
> If that's the case, and nobody here has been able to give you 
> a helpful
> response, maybe it's something to bring up on the 
> nagios-devel list as a
> bug or feature request.
> 
> 
> --------------------------------------------------------------
> -----------
> Using Tomcat but need to do more? Need to support web 
> services, security?
> Get stuff done quickly with pre-integrated technology to make 
> your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on 
> Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&
dat=121642
_______________________________________________
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

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
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