-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 15/08/08 02:13 PM, Jonathan Call wrote: > I did read through that section thoroughly. I set up the check on the > central server and then disabled the check on the distributed server. I > waited for the time limit to expire. I watch the central server set the > next active check time to ~10 minutes after the last check time. But > that time came and went and nothing happened. > > Perhaps this is because I have active checks disabled globally (via > nagios.cfg) on my central server instead of on a per host basis?
Most likely, since freshness checks are actually active checks. If you use templates properly, disabling active checks on all hosts of the central server should be a one-line change. Also, depending on what you're trying to do you may want to use a special check for freshness checking, like: command_line $USER1$/check_dummy 3 "Did not receive $SERVICEDESC$ results" If you want to change the alert level and/or message depending on the service you can pass it as arguments too; ex: command_name check_dummy command_line $USER1$/check_dummy $ARG1$ $ARG2$ And on the service: check_command check_dummy!1!"Did not receive $SERVICEDESC$ results" - -- Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIpj4b6dZ+Kt5BchYRAsWBAJ9oiSNbWutkfflZjpxGiCer/XKg8gCg5nLI 1Cdwd6gey6YclhczTmXkDRo= =IHGh -----END PGP SIGNATURE----- ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ 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
