Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Hi list,
=20
=20
I'm running Nagios 2.5 (not 3 because I use Oreon and It doesn't support
it for the moment
). I've got a lot of distant host, so I useparent/child relation between servers and routers. So I don't receive
notification if the host are in a unreachable state. All is good in the
host level. The problem I've got is that the services of theses servers
are checked. They do not send me alert (no u flag in the service
notification definition), but the information of CRITICAL state is in
the nagios.log. The web interface show me error in theses hosts because
the error is present in the nagios.log.
Is there a way to put service in state UNKNOWN (and do not make the
check) when the host is in an UNREACHABLE state?
=20
I can try to patch, the main service function seem to be the
run_service_check (base/check.c), isn't it?
=20
Thanks,
=20
=20
Jean
=20
PS: thanks a lot, Nagios is a great tool and help me a lot, so if I can
try to help Nagios...
------_=_NextPart_001_01C800DF.7BDDEA77
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Hi list,
I’m running Nagios 2.5 (not 3 because I =
use
Oreon and It doesn’t support it for the moment
). I’ve =got a lot
of distant host, so I use parent/child relation between servers and =
routers. So
I don’t receive notification if the host are in a unreachable =
state. All
is good in the host level. The problem I’ve got is that the =
services of
theses servers are checked. They do not send me alert (no u flag in the =
service
notification definition), but the information of CRITICAL state is in =
the nagios.log.
The web interface show me error in theses hosts because the error is =
present in
the nagios.log.
Is there a way to put service in state UNKNOWN =
(and
do not make the check) when the host is in an UNREACHABLE =
state?
I can try to patch, the main service function =
seem to
be the run_service_check (base/check.c), isn’t =
it?
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]