Host is down but there aren't any further alerts
Quanah Gibson-Mount
quanah at stanford.edu
Tue Jun 15 22:07:13 CEST 2004
--On Monday, June 14, 2004 2:29 PM -0700 Quanah Gibson-Mount
<quanah at stanford.edu> wrote:
>
>
> --On Monday, June 14, 2004 10:19 PM +0200 Andreas Ericsson <ae at op5.se>
> wrote:
>
>>
>> Read up on notification_interval and escalations. It's all well
>> documented.
>
> 1) We don't use escalations.
> 2) The notification interval is just fine. I emailed my config before,
> no one here saw any issues with it. And there have been plenty of people
> who see this issue, and I have yet to see a *single response* that
> addresses a fix to the problem.
define host {
name ldap-host-template
check_command check-host-alive
max_check_attempts 2
notification_interval 30
notification_period 24x7
notification_options d,u,r
register 0
}
As I read that, when the host goes down, check twice. After that, notify.
Continue notifying every 30 minutes, 24 hours a day 7 days a week. I'd be
happy to know if I'm mistaken. It certainly does the first notification --
just never follows up.
--Quanah
--
Quanah Gibson-Mount
Principal Software Developer
ITSS/Shared Services
Stanford University
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html
-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
_______________________________________________
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
More information about the Users
mailing list