[Nagios-users] Passive checks only, how to realy disable active checks without nagios complaining about.

[Benoit Panizzon]

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?

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

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).

Regards
- --
Benoît Panizzon, <***@imp.ch>
- ------------------------------------------------------------------------
ImproWare AG, UNIXSP & ISP Phone: [phone]
Zurlindenstrasse 29 Fax: [phone]
CH-4133 Pratteln Net: http://www.imp.ch/
- ------------------------------------------------------------------------

[Marc Powell]

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

[j***@aracomp.de]

On Behalf Of Marc Powell

...

Post by Benoit Panizzon
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

If you want to produce meaningfull messages follow the docs at:
http://<your-nagios-host>/nagios/docs/freshness.html

There's an example for a script which returns info about backup state.
echo "CRITICAL: Results of backup job were not reported!"


I use:
#!/bin/sh
echo "CRITICAL: Passive check did not send data for a too long time!"
exit 2


Bye,

Joerg