-
Problem report
-
Resolution: Won't fix
-
Trivial
-
None
-
None
-
Zabbix server 5.013
fping 4.2
-
Team A
-
Sprint 86 (Mar 2022), Sprint 87 (Apr 2022), Sprint 88 (May 2022), Sprint 89 (Jun 2022)
-
0.25
Simple Check monitors 100 hosts.
icmpping[,4,3000,,2000]
A single icmp pinger process monitors about 2 to 4 at any given time.
debug log
/usr/bin/fping -C4 -p3000 -t2000 -i0 2>&1 </tmp/zabbix_server_3732.pinger;
debug log
read line [ICMP Host Unreachable from 172.16.10.100 for ICMP Echo sent to xxx.xxx.xxx.2] read line [ICMP Host Unreachable from 172.16.10.100 for ICMP Echo sent to xxx.xxx.xxx.2] read line [ICMP Host Unreachable from 172.16.10.100 for ICMP Echo sent to xxx.xxx.xxx.2] read line [ICMP Host Unreachable from 172.16.10.100 for ICMP Echo sent to xxx.xxx.xxx.2] read line [xxx.xxx.xxx.1 : 5.83 5.94 6.00 5.91] read line [xxx.xxx.xxx.2 : - - - -]
If the same fping is executed directly from the command, -i0 fails and -i1 succeeds.
fping command
# /usr/sbin/fping -C4 -p3000 -t2000 -i0 2>&1 </tmp/zbx_ping.pinger # /usr/sbin/fping -C4 -p3000 -t2000 -i1 2>&1 </tmp/zbx_ping.pinger
Also, the same host is not always unreachable, and the timing varies.
The -i option is set to 0 on first operation, but the automatically set 0 is unstable.
Is it possible to automatically reconfigure the -i option or set it in the icmpping parameters?
