markuslf
commented
1 year ago The ping check is very tolerant - if you send 5 packets, it will even tolerate 4 packet losses (80%), so the check is usually satisfied if there is at least one response to a packet.
But what it will not tolerate is any return code from the built-in ping command other than "0". You have a transmission error (+1 errors), which is reported by ping and therefore also by the plugin.
BTW, the native ping command returns "1" if "(it does not get any packets back) or (number of packets sent is lower than number of packets received and deadline has been reached)".
What does the native ping -c 5 -i 0.2 -w 5 -q 192.168.1.1 tell you?
Beleggrodion
This issue respects the following points:
Which variant of the Monitoring Plugins do you use?
Bug description
I don't know if its directly a bug or more a problem of understanding.
Currently i setup a new nagios instance (with the new icingadb instead of monitoring web plugin) . On the old instance we had the problem that often wrong ping (in my opinion) "down" messages are reported. So on the new instance i switched to your ping check plugin (one other reason was more performance data info). But also the problem exists there too. For comparison, tools like "smokeping" with 10 pings each 30 secs don't see any packet loss, etc. Also fping as probe don't see any issue. (smokeping uses fping)
fping:
ping (i called it ping-ng because ping is the default ping of icinga)
or here for comparisson smokeping output:
So for me, and thats why it looks like a bug is, that if only 1 packet is missing (i can set the count high, etc.) or one has type "error" the state directly "Destination Host Unreachable" but the host is reachable, and working. Also other services don't had problems at all. So it switch between "Critical" and "Ok" without a "Warning" state or that this is realy critical because all other services don't display any issue.
Steps to reproduce - Plugin call
/usr/lib64/nagios/plugins/ping -H 192.168.1.1 --interval=0.2 --count=5 --timeout=5
Steps to reproduce - Data
Destination Host Unreachable. PING 192.168.1.1: 5 packets transmitted, 4 received, +1 errors, 20% packet loss, time 804ms. rtt min/avg/max/mdev = 8.457/8.532/8.600/0.052 ms|'transmitted'=5;;;0; 'received'=4;;;0; 'duplicates'=0;;;0; 'checksum_corrupted'=0;;;0; 'errors'=1;;;0; 'packet_loss'=20%;;;0;100 'time'=804ms;;;0; 'rtt_min'=8.457ms;;;0; 'rtt_avg'=8.532ms;;;0; 'rtt_max'=8.600ms;;;0; 'rtt_mdev'=0.052ms;;;0;
Environment
Linux mon01.rma01.4s-rma.intra 5.15.0-75-generic #82-Ubuntu SMP Tue Jun 6 23:10:23 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Plugin Version
ping: v2023051201 by Linuxfabrik GmbH, Zurich/Switzerland
Python version
No response
List of Python modules
No response
Additional Information
No response