I have tried your solution Kristian, and it got better. I don't get BoxDown 0 d, 00 h, 00 min anymore, but I still get too many alerts with very short time between down and up.
This is an automatically generated message from NAV:
Box volda-myrane1-MB-sw200.hivolda.no (158.38.86.6) is down since 2005-05-28 17:57:27.
This is an automatically generated message from NAV:
Box volda-myrane1-MB-sw200.hivolda.no (158.38.86.6) is up since 2005-05-28 17:58:08.
We where looking forward to the Service-alert function in nav3. But we have the same problem there. I might get an alert that https is down on a server, but if I try that server right away it resond just fine.
Peder Sefland
Kristian Eide kreide@online.no 19.03.2005 12:35:11 >>>
I get many alert with BoxDown 0 d, 00 h, 00 min Sysname IP From To Downtime boxState XXXXX.hivolda.no 158.38.XX.XXX 02:54 18-03-05 02:55
18-03-05
0 d, 00 h, 00 min boxDown
I believe this is due to some debug code that was unfortunately included in a beta release which sets the default wait time for event engine to a very low (5 seconds) value. You can fix this problem by uncommenting the line in
eventEngine.conf which sets the alertTickLength (default is 60 seconds) and restart event engine. Note that there should not be a semicolon at the end of the line, so if there is one remove it.