*******************************************************
Julian Grunnell
Unix Analyst
TD Waterhouse International
Leeds, West Yorkshire
Tel: 0113 346 2824
Extn: 32824
Mobex: 52824
*******************************************************
Yueh-Hung Liu <[email protected]>
09/02/2011 13:26
Please respond to
Nagios Users List <[email protected]>
To
Nagios Users List <[email protected]>
cc
Subject
Re: [Nagios-users] Understanding Unhandled Services / Hosts
because the host is down, it assumes all its service are also unavailable.
therefore the first priority task is to "handle" the problem of the host.
so what i guess is just for simplifying display, only the host which
is down appears in Unhandled section.
On Wed, Feb 9, 2011 at 8:16 PM, <[email protected]> wrote:
>
> Hi - would someone be able to explain in detail the behaviour of this? I
> have a Nagios setup that in the Problems page is showing a host as DOWN
-
> it's currently failing my default FPING test. It also has a number of
simple
> check_tcp commands run against it, all of which are timing out because
> obviously with the host down I'm getting a "CRITICAL - Socket timeout
after
> 10 seconds" for them all. BUT when looking in Unhandled Services they
don't
> appear. The host itself DOES appear in the Unhandled Hosts screen. There
are
> NO comments / acknowledgements in place at all for this host.
>
> Does anyone know why the service checks don't appear as an Unhandled
> Service?
>
> Thanks - J.
>
Thanks, your explanation does make sense as at the time I'd not
acknowledged it, no scheduled downtime or anything. I'll just have to keep
an eye on it for when this happens again or I'll simulate an error when I
get time. I can just about remember that with the HOST critical it
appeared in the "unhandled Hosts" section. And looking at the "Service
Status Details" page the "Attempt" column remained on "1/3" whilst the
host was DOWN. So it certainly was as if the HOST is DOWN so there is no
point in it trying to perform any Service checks as these are always going
to fail.
Julian.
_______________________________________________________
Consider the environment: Please don't print this e-mail unless you really need
to.
Confidentiality: This email and its attachments are intended for the above
named only and may be confidential. If they have come to you in error you must
take no action based on them, nor must you copy or show them to anyone; please
reply to this email and highlight the error.
Viruses: Although we have taken steps to ensure that this email and
attachments are free from any virus, we advise that in keeping with good
computing practice the recipient should ensure that they are actually
virus-free.
Brokerage services provided by TD Waterhouse Investor Services (Europe) Limited
(a subsidiary of The Toronto-Dominion Bank). Authorised and regulated by the
Financial Services Authority (FSA registered number 141282), member of the
London Stock Exchange and the PLUS market. Incorporated in England and Wales
under registration number 2101863. Registered office: Exchange Court, Duncombe
Street, Leeds LS1 4AX. Banking services provided by TD Waterhouse Bank N.V.
authorised and regulated by De Nederlandsche Bank and the Financial Services
Authority for UK Business (FSA registered number 216791). Incorporated in the
Netherlands and registered as a branch in England and Wales under branch
registration number BR006780.
_______________________________________________________
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Nagios-users mailing list
[email protected]
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
