<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0
Transitional//EN">
<HTML><HEAD>
<STYLE type=text/css> P, UL, OL, DL, DIR,
MENU, PRE { margin: 0 auto;}</STYLE>
<META content="MSHTML 6.00.2800.1400" name=GENERATOR></HEAD>
<BODY leftMargin=1 topMargin=1 rightMargin=1><FONT
face=Tahoma size=2>
<DIV>Hi Guys,</DIV>
<DIV> </DIV>
<DIV>I have setup distributed monitoring
across 4 platforms with 1 central server.
The central server is receiving all passive
check results and all seems to be functioning
quite well. I am experiencing one problem
though.I have not turned off active checks
globally as the central server does do some
active checks. The services that are configured
to receive passive checks obviously have
the active checks enabled directive set to
0. However, from the way i understand the
documentation active checks should still
be getting scheduled(even though they are
not executed) this is not the case, meaning
that if i set the freshness checking directives,
active checks will never be executed in the
event of 'stale' results in the ext command
file. It just says N/A in the 'Next Scheduled
Active Check' field. I have studied the
distributed monitoring documentation very
closely and cannot figure out why this is
happening, checked my config many times...</DIV>
<DIV> </DIV>
<DIV>Any suggestions or help would be much
appreciated...</DIV>
<DIV> </DIV>
<DIV>Regards, </DIV>
<DIV>Chris</DIV>
<DIV><BR><BR><BR> </DIV></FONT></BODY></HTML>
-------------------------------------------------------
This SF.Net email is sponsored by: thawte's Crypto Challenge Vl
Crack the code and win a Sony DCRHC40 MiniDV Digital Handycam
Camcorder. More prizes in the weekly Lunch Hour Challenge.
Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m
_______________________________________________
Nagios-users mailing list
Nagios-users@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