[Nagios-devel] freshness checking
Posted: Fri Apr 27, 2007 6:50 am
This is a multi-part message in MIME format.
------_=_NextPart_001_01C788DB.604AB5B8
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Hi,
=20
I am having a problem with freshness checking, while the documentation
says that active checks with freshness enabled should run the active
check only if the check is stale, I cant see it happening, I am using a
lot of passive checks, and the active check is running anyway,=20
=20
I looked at the code for active checks, and there is nothing about
checking for result freshness before running an active check, the only
solution I found was to put check_period to none, but it creates other
problems, disabling active_checks for a service will put it as
"disabled" in the TAC, which is not want I want,
=20
I am running on 2.8 , but looking at 3.0 the code doesn't seem to have
any clause about freshness result checking of active services,
=20
Am I missing something ?=20
=20
Marco.
=20
=20
------_=_NextPart_001_01C788DB.604AB5B8
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Hi,
I am having a problem with freshness checking, while =
the
documentation says that active checks with freshness enabled should run =
the
active check only if the check is stale, I cant see it happening, =
I am
using a lot of passive checks, and the active check is running anyway, =
I looked at the code for active checks, and there is =
nothing
about checking for result freshness before running an active check, the =
only
solution I found was to put check_period to none, but it creates other
problems, disabling active_checks for a service will put it as =
“disabled”
in the TAC, which is not want I want,
I am running on 2.8 , but looking at 3.0 the code =
doesn’t
seem to have any clause about freshness result checking of active =
services,
Am I missing something ? =
<font size=3D2 fa
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
------_=_NextPart_001_01C788DB.604AB5B8
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Hi,
=20
I am having a problem with freshness checking, while the documentation
says that active checks with freshness enabled should run the active
check only if the check is stale, I cant see it happening, I am using a
lot of passive checks, and the active check is running anyway,=20
=20
I looked at the code for active checks, and there is nothing about
checking for result freshness before running an active check, the only
solution I found was to put check_period to none, but it creates other
problems, disabling active_checks for a service will put it as
"disabled" in the TAC, which is not want I want,
=20
I am running on 2.8 , but looking at 3.0 the code doesn't seem to have
any clause about freshness result checking of active services,
=20
Am I missing something ?=20
=20
Marco.
=20
=20
------_=_NextPart_001_01C788DB.604AB5B8
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Hi,
I am having a problem with freshness checking, while =
the
documentation says that active checks with freshness enabled should run =
the
active check only if the check is stale, I cant see it happening, =
I am
using a lot of passive checks, and the active check is running anyway, =
I looked at the code for active checks, and there is =
nothing
about checking for result freshness before running an active check, the =
only
solution I found was to put check_period to none, but it creates other
problems, disabling active_checks for a service will put it as =
“disabled”
in the TAC, which is not want I want,
I am running on 2.8 , but looking at 3.0 the code =
doesn’t
seem to have any clause about freshness result checking of active =
services,
Am I missing something ? =
<font size=3D2 fa
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]