Duplicate host alerts

[Hendrik BŠäcker]

Eli Klein schrieb:
> Correct, there are no running nagios processes after I stop nagios.
> The other two odd behaviors are:
> 
> 1) This host unreachable alert doesn't match my checkcommands.cfg
> notify command and is coming every 30 minutes (10 minutes after the
> other alerts on the very first notify), where all of my
> notification_intervals are set to 60 minutes.
> 
hm... sounds like have "is_volatile 1" in your service defs.
1. Notification: Plugin said CRITICAL with 100% loss
2. Notification: Plugin said CRITICAL but with unreachable


> 2) Even when I disable alerts for all the host's services and for the
> host itself, I still get alerts like this:
> 

The docs doesn't mention that volataile service are ignoring that... so: 
Are you realy sure? ;)

> -----Original Message-----
> From: Nagios Role Account
> Sent: Thursday, May 01, 2008 10:42 PM
> To: Eli Klein
> Subject: ** PROBLEM Host Alert: coswf020 is DOWN **
> 
> ***** Nagios *****
> 
> Notification Type: PROBLEM
> Host: coswf020
> State: DOWN
> Address: 10.34.1.26
> Info: CRITICAL - Host Unreachable (10.34.1.26)
> 
> Date/Time: Thu May 1 22:42:25 MDT 2008
> 
> Thanks for any help!
> 
> -Eli
> 
> On Fri, May 2, 2008 at 6:37 AM, Marc Powell <marc at ena.com> wrote:
>> On May 1, 2008, at 5:35 PM, Eli Klein wrote:
>>> Already got one response to this effect.. unfortunately, there is
>>> definitely only one nagios process running and it's current (if I
>>> stop/start nagios there's only the newest nagios process running).  It
>>> certainly is behaving as though there are two processes running
>>> though.
>> Well, unless you have two different notification commands, both
>> assigned to that contact, that's really the most likely (only?)
>> possibility. I admit this could be a first and a new bug in 3.0.1 but
>> I personally can't understand how it could happen otherwise. Nagios
>> just doesn't retain command{} definitions between restarts and loads
>> them new every time it starts. The fact that it's using an old, and a
>> new, notification command makes this pretty certain. When you stop
>> nagios and view processes, there no nagios process at all?
>>
>> --
>> Marc
>>
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
>> Don't miss this year's exciting event. There's still time to save $100.
>> Use priority code J8TL2D2.
>> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
>> _______________________________________________
>> 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
>>
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
> Don't miss this year's exciting event. There's still time to save $100. 
> Use priority code J8TL2D2. 
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> 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

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
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