submit_check_result always critical

[Robert Gil]

I am setting up a distributed nagios environment for the first time and
have come into a couple road blocks.

 

For some reason the passive checks always come back as critical. From
the command line they show correctly. Also the $OUTPUT$ variable does
not appear to return any information in the submit_check_result script.
I got the script out of the documentation. Perhaps the variable is
incorrect?

 

Here is an example of the email output.

 

 

***** Nagios 2.10 *****

 

Notification Type: PROBLEM

 

Service: Load

Host: Unix Server #rem5

Address: xxx.xxx.xxx.xxx

State: CRITICAL

 

Date/Time: Tue Nov 13 16:32:01 EST 2007

 

Additional Info:

 

OUTPUT

 

 

As you can see above this is version 2.10 using nsca version 2.7.2.

 

Any help would be greatly appreciated. 

 

Thanks,

Rob

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20071113/4992e48e/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
-------------- 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