> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:nagios-users- > [EMAIL PROTECTED] On Behalf Of Aidan Anderson > Sent: Monday, November 19, 2007 7:36 PM > To: [email protected] > Subject: Re: [Nagios-users] Service notifications for a down host? > > Doug Tabb wrote: > > > > I'm looking for a little behavior confirmation here, please. It's my > > understanding that a failed service check is one way a host check is > > initiated. If Nagios determines the host is down, further service > > problem notifications are suppressed. However, I still get one or more > > notifications for the initial service problems. Wouldn't Nagios > > suppress those initial service checks until at least one host check > > has been made? > > > > For illustration, I have a remote site with host parent/child > > relationships configured. If the site goes down, I get about 2 dozen > > service notifications from various child hosts before it realizes the > > top parent host is down and suppresses notifications for that site. I > > then receive the one host recovery along with the 2 dozen or so > > service recovery messages. I had hoped to not receive any service > > notifications in this scenario. Is this expected behavior? > > > > Thank you very much! > > > > Doug Tabb > > > You shouldn't be seeing this behavior. The only time your should see > this is if your services enter a hard state before the hosts. How does > your host retry attempts compare to your service retry attempts? > > Aidan >
That's my problem! Services go to a hard state after one try. Obviously, that's no good. I'll change it. Thanks! -Doug ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Nagios-users mailing list [email protected] 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
