problem state with check_multi

[LEVEAU Stanislas]

Hi,

I created a file with command and state : pix.cmd

command [ pix1 ] = check_icmp -H 1.2.3.4 -w 3000.0,80% -c 5000.0,100% -p 1
command [ pix2 ] = check_icmp -H 1.2.3.5 -w 3000.0,80% -c 5000.0,100% -p 1
command [ pix3 ] = check_icmp -H 1.2.3.6 -w 3000.0,80% -c 5000.0,100% -p 1

state [ OK ] = pix1 == OK && pix2 == OK && pix3 == OK
state [ CRITICAL ] = pix1 == CRITICAL || pix2 == CRITICAL || pix3 == 
CRITICAL


When i run a command with the plugin check_multi the result is UNKNOWN, 
instead of CRITICAL.

# /usr/lib/nagios/plugins/check_multi -f pix.cmd -r 5

UNKNOWN - 3 plugins checked, 2 unknown (pix1, pix2), 1 ok [please don't 
run plugins as root!]
[ 1] pix1 OK - 10.50.184.245: rta 74,980ms, lost 0%
[ 2] pix2 CRITICAL - 217.108.39.122: rta nan, lost 100% [timeout 
encountered after 10s]
[ 3] pix3 CRITICAL - 217.108.39.122: rta nan, lost 100% [timeout 
encountered after 10s]


Have you any idea?
regards
Stan

-- 
*Stanislas LEVEAU**

*Rectorat de Caen
168, rue Caponière
B.P. 6184
14061 CAEN Cedex
	Service Informatique de l'Académie de Caen
Département Systèmes & Réseaux

stanislas.leveau at ac-caen.fr
  Tel : 02.31.30.17.86



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20110704/52a6451d/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
-------------- 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