[Nagios-users] service escalation problems

[Bruce Thayre]

Hello,
I'm not new to nagios, however his is the first nagios installation i 
have done with nagios 3.x.  I've set up several service escalations in 
my services.cfg, they are being recognized and registered with nagios, 
however they are not actually doing anything.  Despite the escalations 
being there, i see each of my services spamming notifications every 30 
minutes.  Is there any additional options i need to enable in Nagios 
3.0.4 to get make the escalations effective.  Or is there any reason 
that when i run nagios -v nagios.cfg and i get this as output:

Nagios 3.0.4
Copyright (c) 1999-2008 Ethan Galstad (http://www.nagios.org)
Last Modified: 10-15-2008
License: GPL

Reading configuration data...

Running pre-flight check on configuration data...

Checking services...
Checked 338 services.
Checking hosts...
Checked 112 hosts.
Checking host groups...
Checked 5 host groups.
Checking service groups...
Checked 0 service groups.
Checking contacts...
Checked 1 contacts.
Checking contact groups...
Checked 1 contact groups.
Checking service escalations...
Checked 973 service escalations.
Checking service dependencies...
Checked 0 service dependencies.
Checking host escalations...
Checked 0 host escalations.
Checking host dependencies...
Checked 0 host dependencies.
Checking commands...
Checked 25 commands.
Checking time periods...
Checked 5 time periods.
Checking for circular paths between hosts...
Checking for circular host and service dependencies...
Checking global event handlers...
Checking obsessive compulsive processor commands...
Checking misc settings...

Total Warnings: 0


So nagios clearly can see the 973 service escalations, they just don't 
seem to be working.  So it would seem my syntax is correct, so an 
example of one of my service escalations (they're all more or less 
identical for different services):

define serviceescalation{
host_name*,!Rambo, !localhost, !nagios, !t2gw04, !uaf-3
service_descriptioncondor_master_alive
first_notification1
last_notification2
notification_interval180
contact_groupsadmins
}


define serviceescalation{
host_name*,!Rambo, !localhost, !nagios, !t2gw04, !uaf-3
service_descriptioncondor_master_alive
first_notification3
last_notification4
notification_interval1440
contact_groupsadmins
}


define serviceescalation{
host_name*,!Rambo, !localhost, !nagios, !t2gw04, !uaf-3
service_descriptioncondor_master_alive
first_notification5
last_notification6
notification_interval0
contact_groupsadmins
}


Any help/input/ridicule would be greatly appreciated.  Thanks!

--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null

Re: [Nagios-users] service escalation problems

[Bruce Thayre]

Hi,
Thanks for the idea, i gave it a shot and it does not seem to be of any 
help.  I was under the impresion that service escalations were for 
taking the nag out of nagios by curbing its tendency to spam admins with 
notifications for large networks, or for specific services.  More 
specifically, if say i don't address a critical state because it's not 
important to me, i don't want to get hourly notifications.  I want a 
reminder after say three hours, maybe another after another three hours, 
and then i want all subsequent reminders to take longer and longer.  Now 
i set this up last time with nagios 2, and had zero issues.  I'm 
wondering if something has changed in nagios 3, or if there is some 
essential step i'm forgetting/missing.  If this continues not working, 
i'll just have to try host escalations, and see if i can do anything 
with those. 
Thanks,
Bruce

Jim Avery wrote:
 2009/5/6 Bruce Thayre btha...@physics.ucsd.edu:

   
 define serviceescalation{
host_name*,!Rambo, !localhost, !nagios, !t2gw04, !uaf-3
service_descriptioncondor_master_alive
first_notification1
last_notification2
notification_interval180
contact_groupsadmins
}
 

 Hmmm.  I don't know if it's the cause of your problem, and I could be
 completely wrong (sorry can't test because I'm at home) but the
 purpose of an escalation is surely to notify an alternative recipient
 if the first (ordinary) notification fails?  I would think if this
 were so then having first_notification = 1 wouldn't make sense.  I'd
 configure the service itself to send the first notification and only
 use escalations for the 2nd or subsequent notifications.

 Other than that I can't see any particular problem with your syntax.
 I would however try setting the escalation_options directive
 explicitly just in case.

 I don't know if, in the absence of an escalation_option directive the
 notification options would be inherited from the service definition.
 A common problem with those is accidentally to include the n option
 which means send no notifications.

 hth,

 Jim

   


--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null