Antwort: Re: Massive HOST UP alerts in nagios.log for no reason

[Sascha.Runschke at gfkl.com]

Andreas Ericsson <ae at op5.se> schrieb am 28.05.2008 13:19:00:

> > The culprit seems to be:
> > 
> > [root at essnagios01 archives]# egrep "HOST ALERT:.*UP;HARD" 
> > nagios-05-28-2008-00.log  | wc -l
> > 97716
> > 
> > So I have 97716 entries each day looking like:
> > 
> > [1211844162] HOST ALERT: sw-00-o2;UP;HARD;1;OK - 1.2.3.4: rta 1,069ms, 

> > lost 0%
> > 
> > with the hostname of course being always different - every host comes 
up 
> > every minute.
> > 
> > Does anyone have any clue if this is intended behaviour or what I may 
have 
> > done wrong?
> > 
> 
> stalking_options is one possible culprit.

Thanks a lot Andreas - this was exactly the reason.
Since I use a self-hacked version of Monarch for administrating nagios 
3.0,
I just missed the fact that it activates stalking for hosts by default on
templates...

regards
Sascha

-- 
Sascha Runschke
Netzwerk-  und  Systemmanagement
Telefon : +49 (201) 102-1879 Mobil : +49 (173) 5419665 Fax : +49 (201) 
102-1102105



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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20080528/15ff0924/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
-------------- next part --------------
_______________________________________________
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