Nagios Support Forum

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_000_01C41009.9B4CACA0
Content-Type: text/plain; charset="utf-8"

Hi Ethan!

I think there is a bug in the notifications logic. I have
notification_interval=0 for all my services. If a service goes from OK to
warning, I get a notification. If it goes from OK to critical, I also get
notified. But if it goes from warning to critical, no notification is
generated.

This patch is for r1.0 (not changed in r1.2), but this patch would also
apply to CVS HEAD.

I've also supplied patches for the documentation to make this clearer. Done
against r1.0.

Ton



This private and confidential e-mail has been sent to you by Egg.
The Egg group of companies includes Egg Banking plc
(registered no. 2999842), Egg Financial Products Ltd (registered
no. 3319027) and Egg Investments Ltd (registered no. 3403963) which
is authorised and regulated by the Financial Services Authority. Egg
Investments Ltd. is entered in the FSA register under number 190518.

Registered in England and Wales. Registered offices: 1 Waterhouse
Square, 138-142 Holborn, London EC1N 2NA.

If you are not the intended recipient of this e-mail and have received
it in error, please notify the sender by replying with 'received in
error' as the subject and then delete it from your mailbox.


------_=_NextPart_000_01C41009.9B4CACA0
Content-Type: application/octet-stream;
name="notifications.html.patch"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="notifications.html.patch"

*** notifications.html Mon Aug 12 02:46:38 2002
--- notifications.html.with_status_change Mon Mar 22 12:09:31 2004
***************
*** 55,61 ****


When a hard state change occurs. More information on state types =
and hard state changes can be found here.
! When a host or service remains in a hard non-OK state and the =
time specified by the <notification_interval> option in =
the host or service definition has passed since the last notification =
was sent out (for that specified host or service). If you don't like =
the idea of recurring notifications, set the =
<notification_interval> value to 0 - this prevents =
notifications from getting sent out more than once for any given =
problem.


=20
--- 55,61 ----


When a hard state change occurs. More information on state types =
and hard state changes can be found here.
! When a host or service remains in a hard non-OK state and the =
time specified by the <notification_interval> option in =
the host or service definition has passed since the last notification =
was sent out (for that specified host or service). If you don't like =
the idea of recurring notifications, set the =
<notification_interval> value to 0 - this prevents =
notifications from getting sent out more than once for any given =
problem unless there was a state change.


=20

------_=_NextPart_000_01C41009.9B4CACA0
Content-Type: application/octet-stream;
name="xoddefault.html.patch"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="xoddefault.html.patch"

*** xoddefault.html Mon Mar 22 12:13:21 2004
--- xoddefault.html.with_state_change Mon Mar 22 12:13:44 2004
***************
*** 129,135 ****

<notification_interval>

! This is the number of "time units" to wait before re-notifying a =
contact that this server is still down or unreachable. Unless =
you've changed the interval_length value in the main configuration file from the default =
value of 60, this number will mean minutes. If you set this value to =
0, Nagios will not re-notify contacts about problems for this =
host - only one problem notification will be sent out.



--- 129,135 ----



...[email truncated]...


This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]