<tt>"MJK Nagios" <mjknagios@mjk.org> schrieb am 29.10.2008 23:11:55: > I seem to be having a rather difficult time getting notifications to > work the way that I would like. I'm using a test host to have Nagios > generate alerts when I take it offline. Nagios detects and sends > notifications for the host coming back on-line very quickly. What I'm > doing in order to test my config is to then simulate that the host > fails again in a few minutes. The problem I'm seeing is that it takes > Nagios 15-20 minutes to send a notification that the host is again > down. This would be useless to me in a production environment; if the > host drops again -- I need to know about it immediately. </tt> <tt>I can't really believe the 2 scenarios you are describing.</tt> <tt>You say the first simulated down comes immediatly and the next simulated</tt> <tt>down takes 15 minutes to notify... that can't be.</tt> <tt>Looking at the history you posted it seems quite obvious to me that</tt> <tt>you have defined 10 retries for the host. With a retry interval of</tt> <tt>roundabout 1 minute (which is sometimes delayed due to scheduler latency)</tt> <tt>you end up with 10-15 minutes until the host enters a HARD state and</tt> <tt>nagios generates a notification.</tt> <tt>Your setup is working exactly how you configurated it.</tt> <tt>If you need immediate notifications, reduce the retry_checks to 1.</tt> <tt>Regards</tt> <tt> Sascha</tt> -- Sascha Runschke IT-Infrastruktur fon : +49 (201) / 102-1879 fax : +49 (201) / 102-1102105 mobil : +49 (173) / 5419665 GFKL Financial Services AG Vorstand: Dr. Peter Jänsch (Vors.), Jürgen Baltes, Dr. Till Ergenzinger, Dr. Tom Haverkamp Vorsitzender des Aufsichtsrats: Dr. Georg F. Thoma Sitz: Limbecker Platz 1, 45127 Essen, Amtsgericht Essen, HRB 13522