Re: [Nagios-devel] freshness checking
Posted: Fri Apr 27, 2007 12:50 pm
Hi,
On 4/27/2007 4:50 PM, Marco Supino wrote:
>=20
>=20
> Hi,
>=20
> =20
>=20
> I am having a problem with freshness checking, while the documentation =
> says that active checks with freshness enabled should run the active=20
> check only if the check is stale, I cant see it happening, I am using =
a=20
> lot of passive checks, and the active check is running anyway,
Looks like you still have active checks enabled. These need to be turned =
off, IIRC.
> =20
>=20
> I looked at the code for active checks,=20
Better look at the manual
that's where I got my knowledge from, and=20
it works correctly, here.
>and there is nothing about=20
> 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=20
> =93disabled=94 in the TAC, which is not want I want,
=2E.. but what you get. That's the way things are in Nagios. Notification=
=20
are created as expected, and I don't consider the tactical overview the=20
most useful report Nagios can deliver.
IIRC, there are patches available for this situation - search he list=20
archives!
Arno
--=20
IT-Service Lehmann [email protected]
Arno Lehmann http://www.its-lehmann.de
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
On 4/27/2007 4:50 PM, Marco Supino wrote:
>=20
>=20
> Hi,
>=20
> =20
>=20
> I am having a problem with freshness checking, while the documentation =
> says that active checks with freshness enabled should run the active=20
> check only if the check is stale, I cant see it happening, I am using =
a=20
> lot of passive checks, and the active check is running anyway,
Looks like you still have active checks enabled. These need to be turned =
off, IIRC.
> =20
>=20
> I looked at the code for active checks,=20
Better look at the manual
that's where I got my knowledge from, and=20it works correctly, here.
>and there is nothing about=20
> 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=20
> =93disabled=94 in the TAC, which is not want I want,
=2E.. but what you get. That's the way things are in Nagios. Notification=
=20
are created as expected, and I don't consider the tactical overview the=20
most useful report Nagios can deliver.
IIRC, there are patches available for this situation - search he list=20
archives!
Arno
--=20
IT-Service Lehmann [email protected]
Arno Lehmann http://www.its-lehmann.de
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]