Nagios Support Forum

If it's not neccessary for someone else to confirm to have same issues, I would appreciate if you'd open the bugreport.
Thanks.

This is the command I used :
Where 10.60.60.228 is the IP of my Nagios host.

As I said earlier, the packets are not leaving Nagios host's interface/NIC, they are not going out on the network so the problem is definitely on the source. Instead of 30 ICMP requests, tcpdump catches less, and at that occasions the results calculations are incorrect. There are no drops/errors on ...

I think we maybe misunderstood each other.
The real issue is that occasionally, when using check_icmp, not all of those packets are sent out on the network (regardless of their number).

Anyway, I can agree with the bug report you submitted, but as a seperate issue.

Command line is identical, except for the ( -4, --use-ipv4): $USER1$/check_icmp -H $HOSTADDRESS$ -w 3000.0,80% -c 5000.0,100% One thing to note is that in that time of trouble I had both check_icmp and check_ping host/service checks configured. I have also noticed that check_icmp sends all packets a...

I apologize for somewhat late reply. Here are the parts of nagios config files that might interest you. But I see nothing wrong neither in configuration nor behaviour (ping works that way, sends as much packets it can in the time window specified until it gets exact number of replies as specified). ...

Hello! We have recently upgraded from Nagios 3.2.1 to Nagios 4.1.1. and are experiencing false check_ping results: hosts that are dead as a doornail get occasional "PING OK - Packet loss = 78%, RTA = 6.55 ms" results for host alive checks. When plugin on the next check returns true: "...