HOST DOWN notification not getting resent

[Andy Vance]

although this may have not been a bug I never found the "misconfiguration"
that was causing this.  I did however find a workaround that allows me to
receive multiple notifications from my service checks even though the host
is down.

I removed the check_command from the host definition and now the host is
always assumed up.

Andy
-----Original Message-----
From: Andy Vance [mailto:avance at speakeasy.net]
Sent: Monday, September 27, 2004 7:31 AM
To: nagios-users at lists.sourceforge.net
Subject: Re: Re: HOST DOWN notification not getting resent


Gerd,
  Thanks for the response.  Yes I did confirm my generic-user didn't have
notification-interval set to 0.

Here is the template in question...

# Generic host definition template
define host{
        name                            generic-host
        notifications_enabled           1       ; Host notifications are
enabled
        event_handler_enabled           1       ; Host event handler is
enabled
        flap_detection_enabled          1       ; Flap detection is enabled
        process_perf_data               1       ; Process performance data
        retain_status_information       1       ; Retain status information
across program restarts
        retain_nonstatus_information    1       ; Retain non-status
information across program restarts
        register                        0       ; DONT REGISTER THIS
DEFINITION - ITS NOT A REAL HOST, JUST A TEMPLATE!
        }

Andy



-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
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