Passive checks only, how to realy disable active checks without nagios complaining about.

[Marc Powell]

Benoit Panizzon <mailto:Benoit.Panizzon at imp.ch> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi all
> 
> After managing to solve the problem on how to submit passive checks
> from plugins on remote hosts via NSCA I run in a new problem... 
> 
> I have to define a check_command even for passive checks but disable
> active checks. (So i used the check_dummy 3 plugin) Of course I use
> the frehsness options.  
> 
> Now nagios dislays nasty red messages that active checks are disabled.
> Is there a way to tell nagios that it's OK that they are disabled and
> not show them so users could get the idea of enabling them? 

Enable active checks but set the check_period to 'none'.

> Is there a way to disable the possibility to enable active checks via
> the web GUI for checks that should only be submitted passively? 

See above.

> The last problem I get is that after the freshness tereshold has
> expired, according to the docs, nagios dies a forced active check of
> the service, which is quite useless as it just uses a dummy check
> command (which can return 'Unknown', but that only helps a little).   

What are you trying to accomplish? If you want the plugin to return
critical instead of warning if the freshness has expired then use
'check_dummy 2' to return a CRITICAL state.

--
Marc 


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_idG21&alloc_id040&op=click
_______________________________________________
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