Massive HOST UP alerts in nagios.log for no reason

[Andreas Ericsson]

Sascha.Runschke at gfkl.com wrote:
> Hi all,
> 
> ever since I started building up our new nagios environment under nagios 
> 3.0, I noticed that my
> logfile contains massive amounts of HOST UP alerts - even though the host 
> was never down before.
> Actually I seem to have this log entry each time a host is checked, I 
> guess they get checked for
> the predictive and cache host tests. But sadly it's getting a real pain, 
> since the logfile is growing
> so big, that my firefox even crashes when I try to view it with the 
> webinterface.
> My daily nagios.log has the massive amount of roundabout 110.000 entries 
> each day - which is
> little bit too much for its 400 hosts / 1600 services imho. Nearly the 
> same checks (actually a few
> less, but whatever) produce roundabout 10.000 lines of log on our nagios 
> 2.11 server each day.
> 
> 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.

-- 
Andreas Ericsson                   andreas.ericsson at op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

-------------------------------------------------------------------------
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/
_______________________________________________
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