Checking and going critical on passive servicecheck-in tardiness?

[ffwqe efwa]

Sorry, you are correct, but I am using 2 and it still doesn't work.  I
accidentally put 3 in my message.
Executing this command does not return critical in Nagios.


# Check/alert for Freshness.
define command{
command_name check_outofdate
command_line $USER1$/check_dummy 2 "CRITICAL: Host has not checked in with
check results in the last 15 minutes.  Host is down or no longer being
monitor by NAGIOS."
}



On 3/16/07, Morris, Patrick <patrick.morris at hp.com> wrote:
>
>
> >      I have various services which provide pasive results to
> > Nagios.  I want to know or assume that any service which has
> > not checked in in over 30 minutes is tardy and crticical.  I
> > tried making it use "check_dummy 3 warning ncnet dead" with
> > the check_freshness_ option and I can't seem to get dummy to
> > generate any critical alerts.
> >
> > Can someone please provide an example of a working setup that
> > will achieve what I'm looking for?
>
> The return code for critical is 2.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20070321/ac2f85a9/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
-------------- next part --------------
_______________________________________________
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