Service Went Down, No notification sent...

[Andreas Ericsson]

John McGowan wrote:
> I'm not sure exactly where to start on this.... last night i checked on 
> my services and noticed a service that was down and had been down for 
> about 20 minutes.  No notification was ever sent out... this is what I 
> saw in the log...
> 
> [08-10-2005 22:07:36] SERVICE ALERT: tessweb;Tessitura 
> SeatServer;CRITICAL;HARD;1;CRITICAL - Socket timeout after 10 seconds
> 
> When I ran a test this morning this is what I saw in the event log.
> 
  > The first thing that stood out when I saw it was the fact that the max
> check attempts didn't seem to make a difference last night... the 
> service went critical hard on the first failure...
> 

This is because the host was down as well. Service checks aren't 
reported if the host is down, and they're set to HARD immediately to 
save the added strain of having to re-check them frequently.

> FYI: the particular thing that caused this failure last night was that 
> the VPN between here and there was down.
> 

So the hostcheck couldn't possibly have succeeded then, and the host was 
most likely in UNREACHABLE state (if you monitor the VPN tunnel in both 
ends and have parents set up properly).

What notifications *did* you get? An unreachable for the VPN tunnel?

-- 
Andreas Ericsson                   andreas.ericsson at op5.se
OP5 AB                             www.op5.se
Lead Developer


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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