several host notifications for 1 host

[Joerg Linge]

Am Mittwoch, 23. Mai 2007 16:31 schrieb Thomas Guyot-Sionnest:
> > -----Original Message-----
> > From: nagios-devel-bounces at lists.sourceforge.net [mailto:nagios-devel-
> > bounces at lists.sourceforge.net] On Behalf Of Joerg Linge
> > Sent: May 23, 2007 9:24
> > To: Nagios Developers List
> > Subject: Re: [Nagios-devel] several host notifications for 1 host
> > 
> > Am Mittwoch, 23. Mai 2007 14:55 schrieb Markus Blum:
> > > Hello,
> > >
> > > i get several notifications after a host went down even
> > notification_interval is defined as 0. It seems to be related to service
> > checks on these host because other hosts, without service checks, work
> > fine. I know service checks will cause a host check but even then there
> > shouldn't  be a notification before the host check returns  a hard state,
> > right ?
> > 
> > Hi Markus,
> > 
> > i think you are talking about Nagios 3.0a4 right ?
> > The same Situation on my system running nagios 3.0a4 CVS 2007-05-23
> > 
> > Host Down Notifications are sent on HARD and SOFT states.
> 
> According to Nagios documentation both 2.x and 3.x:
> 
> notification_interval: 	This directive is used to define 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 directive 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.

Yes thats right. Notification interval and is_volatile are both set to 0 for this Host

> Looks like this is a bug... Does it keep notifying after in enters a HARD
> state? If no, then setting "max_check_attempts 1" will fix your problem.
> SOFT states on service check failures are sending notifications anyways.

We are talking about HOST notifications.
Soft Host States are a new 3.x feature.

No, max_check_attempts is set to 10. No more notifications if the  
HARD state is reached.

I have turned on debug level 32 for notifications and every SOFT  
state results in a notification.

DEBUG Log:
1179983462.267951:032.0] ** Host Notification Attempt ** Host: 'kassel-srv3-3', Type: 0, Current State: 1, Last Notification: Thu Jan  1 01:00:00 1970
[1179983462.267992:032.0] Notification viability test passed.
[1179983462.268006:032.1] Current notification number: 1
[1179983462.268019:032.2] Creating list of contacts to be notified.
[1179983462.268033:032.1] Host notification will NOT be escalated.
[1179983462.268047:032.2] Adding contact 'nagiosadmin' to notification list.
[1179983462.268433:032.2] ** Checking host notification viability for contact 'nagiosadmin'...
[1179983462.268464:032.2] ** Host notification viability for contact 'nagiosadmin' PASSED.
[1179983462.268478:032.2] ** Notifying contact 'nagiosadmin'
[1179983462.268577:032.2] Raw Command: /usr/bin/printf "%b" "***** Nagios *****....
[1179983462.268591:032.2] Processed Command: /usr/bin/printf "%b" "***** Nagios ***** ....
[1179983462.327568:032.2] Calculating next valid notification time...
[1179983462.327610:032.2] Default interval: 16384
[1179983462.327626:032.2] Interval used for calculating next valid notification time: 0.000000
[1179983462.327658:032.0] No contacts were notified.  Next possible notification time: Thu May 24 07:11:02 2007
[1179983462.327672:032.0] 1 contacts were notified.
[....]
[1179983582.127427:032.0] ** Host Notification Attempt ** Host: 'kassel-srv3-3', Type: 0, Current State: 1, Last Notification: Thu Jan  1 01:00:00 1970
[1179983582.127474:032.0] Notification viability test passed.
[1179983582.127491:032.1] Current notification number: 2
[1179983582.127504:032.2] Creating list of contacts to be notified.
[1179983582.127514:032.1] Host notification will NOT be escalated.
[1179983582.127526:032.2] Adding contact 'nagiosadmin' to notification list.
[1179983582.128059:032.2] ** Attempting to notifying contact 'nagiosadmin'...
[1179983582.128075:032.2] ** Checking host notification viability for contact 'nagiosadmin'...
[1179983582.128098:032.2] ** Host notification viability for contact 'nagiosadmin' PASSED.
[1179983582.128109:032.2] ** Notifying contact 'nagiosadmin'
[1179983582.128201:032.2] Raw Command: /usr/bin/printf "%b" "***** Nagios *****\
[1179983582.128212:032.2] Processed Command: /usr/bin/printf "%b" "***** Nagios *****
[1179983582.149671:032.2] Calculating next valid notification time...
[1179983582.149705:032.2] Default interval: 16384
[1179983582.149719:032.2] Interval used for calculating next valid notification time: 0.000000
[1179983582.149768:032.0] No contacts were notified.  Next possible notification time: Thu May 24 07:13:02 2007
[1179983582.149781:032.0] 1 contacts were notified.

Jörg

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/