service escalation problems

[Jim Avery]

2009/5/6 Bruce Thayre <bthayre at physics.ucsd.edu>:

> define serviceescalation{
>    host_name        *,!Rambo, !localhost, !nagios, !t2gw04, !uaf-3
>    service_description    condor_master_alive
>    first_notification    1
>    last_notification    2
>    notification_interval    180
>    contact_groups        admins
>    }

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 at 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