Are you using freshness checking? If not, try creating a time period "never" so that the active check is never scheduled.<div><br></div><div>Otherwise you usually just want to set active_checks_enabled to 0 but I guess you don't want the CGIs to show that the checks are disabled?</div> <div><br></div><div>Regards</div><div>Martin Melin<br><div><br><div class="gmail_quote">On Mon, Oct 5, 2009 at 10:01 AM, Getchell, Kristoffer M <span dir="ltr"><<a href="mailto:K.Getchell@kingston.ac.uk">K.Getchell@kingston.ac.uk</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">I should possibly add that we're using Nagios 3.0.6 on SLES 11 if that makes any difference.<br> <br> Cheers,<br> <br> <br> <br> <br> Kris<br> <div><div></div><div class="h5"><br> <br> <br> -----Original Message-----<br> From: Getchell, Kristoffer M [mailto:<a href="mailto:K.Getchell@kingston.ac.uk">K.Getchell@kingston.ac.uk</a>]<br> Sent: 05 October 2009 00:16<br> To: <a href="mailto:nagios-users@lists.sourceforge.net">nagios-users@lists.sourceforge.net</a><br> Subject: [Nagios-users] Service Definition for Passive Only Reports<br> <br> We have a number of service which I don't want Nagios to actively monitor, instead Nagios will be updated by passive alerts which are generated by the service itself.<br> <br> I've currently got a service definition setup, but haven't figured out how to get the service to not have an active check associated with it without any warnings being issued in the tactical overview page. At the moment what i've done is setup an active check that does nothing and set a long between times check. However, this isn't ideal.<br> <br> Has anyone else setup a passive only service and managed to get the tactical overivew interface to not complain about active checks not being enabled on a specific host/service?<br> <br> Many thanks,<br> <br> <br> <br> <br> Kris<br> <br> This email has been scanned for all viruses by the MessageLabs Email<br> Security System.<br> <br> ------------------------------------------------------------------------------<br> Come build with us! The BlackBerry® Developer Conference in SF, CA<br> is the only developer event you need to attend this year. Jumpstart your<br> developing skills, take BlackBerry mobile applications to market and stay<br> ahead of the curve. Join us from November 9-12, 2009. Register now!<br> <a href="http://p.sf.net/sfu/devconf" target="_blank">http://p.sf.net/sfu/devconf</a><br> _______________________________________________<br> Nagios-users mailing list<br> <a href="mailto:Nagios-users@lists.sourceforge.net">Nagios-users@lists.sourceforge.net</a><br> <a href="https://lists.sourceforge.net/lists/listinfo/nagios-users" target="_blank">https://lists.sourceforge.net/lists/listinfo/nagios-users</a><br> ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue.<br> ::: Messages without supporting info will risk being sent to /dev/null<br> <br> This email has been scanned for all viruses by the MessageLabs Email<br> Security System.<br> <br> This email has been scanned for all viruses by the MessageLabs Email<br> Security System.<br> <br> ------------------------------------------------------------------------------<br> Come build with us! The BlackBerry® Developer Conference in SF, CA<br> is the only developer event you need to attend this year. Jumpstart your<br> developing skills, take BlackBerry mobile applications to market and stay<br> ahead of the curve. Join us from November 9-12, 2009. Register now!<br> <a href="http://p.sf.net/sfu/devconf" target="_blank">http://p.sf.net/sfu/devconf</a><br> _______________________________________________<br> Nagios-users mailing list<br> <a href="mailto:Nagios-users@lists.sourceforge.net">Nagios-users@lists.sourceforge.net</a><br> <a href="https://lists.sourceforge.net/lists/listinfo/nagios-users" target="_blank">https://lists.sourceforge.net/lists/listinfo/nagios-users</a><br> ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue.<br> ::: Messages without supporting info will risk being sent to /dev/null<br> </div></div></blockquote></div><br></div></div>