Re: [Nagios-devel] notification_interval check vs. check_period
Posted: Fri Sep 12, 2008 12:56 pm
------=_Part_70095_1230376.1221253016176
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Oops,
On Fri, Sep 12, 2008 at 5:35 PM, Marcel wrote:
> Yes,
>
> On Fri, Sep 12, 2008 at 6:13 AM, Hendrik B=8A=E4cker wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Hi,
>>
>> Marcel schrieb:
>> > I think i've found a bug.
>> >
>> > in config.c:
>> >
>> > At line #1878, temp_service->check_interval is incorrectly assuming
>> > interval_lenght=3D60, but if one would use an interval_length directiv=
e
>> > equals to 1, then the Warnings like: "[1220575781] Warning: Service
>> > 'Current Load' on host 'faeroes' has a notification interval less tha=
n
>> > its check interval! Notifications are only re-sent after checks are
>> > made, so the effective notification interval will be that of the check
>> > interval." will incorrectly shows up, because the conditional below
>> > assumes interval_lenght =3D 60.
>> >
>> Do have a configuration example to rebuild your mentioned problem?
>> I am using interval_length=3D1 and doesn't recognize any of your warning
>> messages cause of mismatching check/notification interval.
>
>
>
> If you have a service that would be checked every 10 seconds, and
> notification interval =3D 60, then you should get the warning message.
>
I think a bit and that would not be the case, but instead, not 10 seconds,
but like 300 (or five minutes if interval_length=3D1). Then the warning is
issued.
>
>
> And yes, it is against 3.0.3 cvs code.
>
> Cheers
> Marcel
>
>
------=_Part_70095_1230376.1221253016176
Content-Type: text/html; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Oops,On Fri, Sep 12, 20=
08 at 5:35 PM, Marcel <[email protected]> wrote:
Yes,On Fri, Sep 12, 2008 at 6:13 AM, Hendrik B=8A=E4cker &=
lt;andurin@pro=
cess-zero.de> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Marcel schrieb:
> I think i've found a bug.
>
> in config.c:
>
> At line #1878, temp_service->check_interval is incorrectly assuming=
> interval_lenght=3D60, but if one would use an interval_length directiv=
e
> equals to 1, then the Warnings like: "[1220575781] Warning: Servi=
ce
> 'Current Load' on host 'faeroes' has a notificat=
ion interval less than
> its check interval! Notifications are only re-sent after checks =
are
> made, so the effective notification interval will be that of the check=
> interval." will incorrectly shows up, because the conditional bel=
ow
> assumes interval_lenght =3D 60.
>
Do have a configuration example to rebuild your mentioned problem?
I am using interval_length=3D1 and doesn't recognize any of your warnin=
g
messages cause of mismatching check/notification interval.If you have a service that would be checked every 10 seconds=
, and notification interval =3D 60, then you should get the warning message=
.
I think a bit and that would not be the c=
ase, but instead, not 10 seconds, but like 300 (or five minutes if interval=
_length=3D1). Then the warning is issued. <blockquote class=3D"gm=
ail_quote" style=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt =
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Oops,
On Fri, Sep 12, 2008 at 5:35 PM, Marcel wrote:
> Yes,
>
> On Fri, Sep 12, 2008 at 6:13 AM, Hendrik B=8A=E4cker wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Hi,
>>
>> Marcel schrieb:
>> > I think i've found a bug.
>> >
>> > in config.c:
>> >
>> > At line #1878, temp_service->check_interval is incorrectly assuming
>> > interval_lenght=3D60, but if one would use an interval_length directiv=
e
>> > equals to 1, then the Warnings like: "[1220575781] Warning: Service
>> > 'Current Load' on host 'faeroes' has a notification interval less tha=
n
>> > its check interval! Notifications are only re-sent after checks are
>> > made, so the effective notification interval will be that of the check
>> > interval." will incorrectly shows up, because the conditional below
>> > assumes interval_lenght =3D 60.
>> >
>> Do have a configuration example to rebuild your mentioned problem?
>> I am using interval_length=3D1 and doesn't recognize any of your warning
>> messages cause of mismatching check/notification interval.
>
>
>
> If you have a service that would be checked every 10 seconds, and
> notification interval =3D 60, then you should get the warning message.
>
I think a bit and that would not be the case, but instead, not 10 seconds,
but like 300 (or five minutes if interval_length=3D1). Then the warning is
issued.
>
>
> And yes, it is against 3.0.3 cvs code.
>
> Cheers
> Marcel
>
>
------=_Part_70095_1230376.1221253016176
Content-Type: text/html; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Oops,On Fri, Sep 12, 20=
08 at 5:35 PM, Marcel <[email protected]> wrote:
Yes,On Fri, Sep 12, 2008 at 6:13 AM, Hendrik B=8A=E4cker &=
lt;andurin@pro=
cess-zero.de> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Marcel schrieb:
> I think i've found a bug.
>
> in config.c:
>
> At line #1878, temp_service->check_interval is incorrectly assuming=
> interval_lenght=3D60, but if one would use an interval_length directiv=
e
> equals to 1, then the Warnings like: "[1220575781] Warning: Servi=
ce
> 'Current Load' on host 'faeroes' has a notificat=
ion interval less than
> its check interval! Notifications are only re-sent after checks =
are
> made, so the effective notification interval will be that of the check=
> interval." will incorrectly shows up, because the conditional bel=
ow
> assumes interval_lenght =3D 60.
>
Do have a configuration example to rebuild your mentioned problem?
I am using interval_length=3D1 and doesn't recognize any of your warnin=
g
messages cause of mismatching check/notification interval.If you have a service that would be checked every 10 seconds=
, and notification interval =3D 60, then you should get the warning message=
.
I think a bit and that would not be the c=
ase, but instead, not 10 seconds, but like 300 (or five minutes if interval=
_length=3D1). Then the warning is issued. <blockquote class=3D"gm=
ail_quote" style=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt =
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]