Default value for use_agressive_host_checking (bug-like propertie s)

[Voon, Ton]

Ethan,

I think it is more wasteful to be forced to add a check_ping service - which
is continually checking - to every host. I was concerned that the perception
is that Nagios is reporting "incorrect" information. According to the host
details screen, it says it was last status checked at time x, when there
wasn't really a check because of use_agressive_host=0.

In fact, if I add a ping service check to a host and every other service on
that host was failing, current (1.0) code says if a service fails, do a
check-host-alive (as the ping service works, so the host is now considered
up). This seems to me as the same amount of pings as a use_agressive_host=1
without a ping-service-check, so it doesn't seem more efficient in this
scenario.

What about this as a possible long-term solution: Queue the
host-check-alives so that if one is requested within a minimum period, it is
disregarded (this would also help if half the services were failing on a
host which is up). However, the cost is more development time.

Ton

> -----Original Message-----
> From: Ethan Galstad [mailto:nagios at nagios.org] 
> Sent: Friday, August 01, 2003 5:02 AM
> To: nagios-users at lists.sourceforge.net
> Subject: Re: [Nagios-users] Default value for 
> use_agressive_host_checking (bug-like propertie s)
> 
> 
> This is a good example of how Nagios works.  In order to optimize 
> host checks, a host that is not up is not (usually) checked to see if 
> it has recovered unless one of it's services changes state after it 
> has gone down.  A simple solution for this case would be to add a 
> PING check service to the host.
> 
> The use_agressive_host_checking makes Nagios re-check the status of a 
> DOWN or UNREACHABLE host every time a check is made of one of its 
> services.  This is a grossly inefficient way of doing things for 
> 99.9% of all setups out there, but it can be useful.
> 
> 
> On 30 Jul 2003 at 12:44, Voon, Ton wrote:
> 
> > Hi!
> > 
> > Wanted to see what other people thought about this because 
> it looked like a
> > bug to me until I found the use_agressive_host_checking parameter.
> > 
> > I found a situation where a host uses only NRPE to do its 
> service checks.
> > NRPE is stopped as part of a reboot, so all services are 
> marked as CRITICAL
> > and the host is DOWN. When the host boots up, NRPE fails to restart.
> > However, the host is always considered as DOWN, even though 
> pings do work,
> > because the host check is not run unless 
> use_agressive_host_checking is set
> > to 1.
> > 
> > I understand there are performance improvements by settign 
> this to 0, but
> > Nagios appears to be reporting wrong information and that 
> is bad publicity.
> > Do people think it is a good idea for the default of
> > use_agressive_host_checking to be 1?
> > 
> > Ton
> > 
> > 
> > This private and confidential e-mail has been sent to you by Egg.
> > The Egg group of companies includes Egg Banking plc
> > (registered no. 2999842), Egg Financial Products Ltd (registered
> > no. 3319027) and Egg Investments Ltd (registered no. 3403963) which
> > carries out investment business on behalf of Egg and is regulated
> > by the Financial Services Authority.  
> > Registered in England and Wales. Registered offices: 1 
> Waterhouse Square,
> > 138-142 Holborn, London EC1N 2NA.
> > If you are not the intended recipient of this e-mail and have
> > received it in error, please notify the sender by replying with
> > 'received in error' as the subject and then delete it from your
> > mailbox.
> > 
> > 
> > 
> > -------------------------------------------------------
> > This SF.Net email sponsored by: Free pre-built ASP.NET 
> sites including
> > Data Reports, E-commerce, Portals, and Forums are available now.
> > Download today and enter to win an XBOX or Visual Studio .NET.
> > 
> http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet
_072303_01/01
> _______________________________________________
> 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
> 



Ethan Galstad,
Nagios Developer
---
Email: nagios at nagios.org
Website: http://www.nagios.org



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
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


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
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