[Nagiosplug-help] check_ping critical you need more args could not pipe

[Thomas Guyot-Sionnest]

On 18/01/07 05:17 PM, Don Munyak wrote:
> On 1/17/07, Thomas Guyot-Sionnest <dermoth at aei.ca> wrote:
>>
>> I played with check_ping a little bit, and as far as I know it writes
>> something like "Could not interpret result from ping" when there's
>> something wrong...
>>
>> I'm wondering how the output of ping could end up on check_ping's output
>> since the child's stdout AND stderr are both grabbed bt check_ping...
>>
>> Don Munyak, if you want to verify whenever the actual ping ran and with
>> which args, you can add "-vvv" to the check_ping command and running it
>> from the command line. You should (shouldn't in your particular case)
>> get something like this:
>>
>> $ plugins/check_ping -H localhost -w1000,10% -c2000,20% -p1 -vvv
>> CMD: /bin/ping -n -U -w 10 -c 1 localhost
>> Output: PING localhost (127.0.0.1) 56(84) bytes of data.
>> Output: 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.037 ms
>> Output:
>> Output: --- localhost ping statistics ---
>> Output: 1 packets transmitted, 1 received, 0% packet loss, time 0ms
>> Output: rtt min/avg/max/mdev = 0.037/0.037/0.037/0.000 ms
>> PING OK - Packet loss = 0%, RTA = 0.04 ms
>> 1000.000000:10% 2000.000000:20%
>> $
>>
>>
>> Thomas
>>
> 
> 
> Hope this helps some, because I do appreciate your help so far.
> 
> [ check_icmp]
> 
> don-bsd# /usr/local/libexec/nagios/check_ping -v -H 127.0.0.1 -w
> 100.0,20% -c 500.0,60% -p 5
> setsockopt failed
> Setting alarm timeout to 10 seconds
> packets: 5, targets: 1
> target_interval: 0.000, pkt_interval 80.000
> crit.rta: 500.000
> max_completion_time: 3400.000
> crit = {500000, 60%}, warn = {100000, 20%}
> pkt_interval: 80000  target_interval: 0  retry_interval: 0
> icmp_pkt_size: 64  timeout: 10
> 0.668 ms rtt from 127.0.0.1, outgoing ttl: 64, incoming ttl: 64
> 0.246 ms rtt from 127.0.0.1, outgoing ttl: 64, incoming ttl: 64
> 0.211 ms rtt from 127.0.0.1, outgoing ttl: 64, incoming ttl: 64
> 0.262 ms rtt from 127.0.0.1, outgoing ttl: 64, incoming ttl: 64
> 0.209 ms rtt from 127.0.0.1, outgoing ttl: 64, incoming ttl: 64
> icmp_sent: 5  icmp_recv: 5  icmp_lost: 0
> targets: 1  targets_alive: 1
> OK -
> 127.0.0.1: rta 0.319ms, lost 0%|
> rta=0.319ms;100.000;500.000;0; pl=0%;20;60;;
> targets: 1, targets_alive: 1
> 
> [check_ping]
> 
> don-bsd# /usr/local/libexec/nagios/check_ping -v -H 127.0.0.1 -w
> 100.0,20% -c 500.0,60% -p 5
> CRITICAL - You need more args!!!
> Could not open pipe:
> 
> don-bsd# pwd
> /usr/local/libexec/nagios
> 
> don-bsd# ./check_ping -H localhost -w1000,10% -c2000,20% -p1 -vvv
> CMD:
> CRITICAL - You need more args!!!
> Could not open pipe:

Unfortunately that's either a *very* old version of check_ping (I
checked v 1.4, check ping last modified on 2004-12-29 and it showed the
current behavior) or a version that's not from nagios_plugins.

I'm sorry but I can't help you with this particular release. The two
solutions that you have are:

1. Uninstall completly FreeBSD Ports Nagios/Nagios-plugins, download the
latest source for Nagios and Nagios-plugins from http://www.nagios.org,
compile it and install it according to the instructions in Nagios
documentation found here:

http://nagios.sourceforge.net/docs/2_0/installing.html

2. Try to get support from FreeBSD Ports maintainers/developers.

Thomas