[ZBX-25839] fping issues Created: 2025 Jan 07  Updated: 2025 Jan 13

Status: Need info
Project: ZABBIX BUGS AND ISSUES
Component/s: Server (S)
Affects Version/s: 7.2.2
Fix Version/s: None

Type: Incident report Priority: Trivial
Reporter: zabbix_1993 Assignee: Jan Prusinowski
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

ubuntu22.04;zabbix7.2.2


Attachments: PNG File image-2025-01-08-01-23-02-081.png     PNG File image-2025-01-08-01-23-41-656.png     PNG File image-2025-01-08-01-24-15-471.png     PNG File image-2025-01-08-01-24-55-801.png     PNG File image-2025-01-08-21-41-59-075.png     PNG File image-2025-01-09-23-06-06-490.png     PNG File image-2025-01-09-23-09-58-271.png     PNG File image-2025-01-10-00-16-49-204.png     PNG File image-2025-01-10-22-37-51-922.png     Text File zabbix-server.log    
Issue Links:
Duplicate
duplicates ZBX-22833 Zabbix Server Docker : sh: /usr/sbin/... Closed

 Description   

zabbix-server.conf



 Comments   
Comment by Alexander Vladishev [ 2025 Jan 08 ]

Could you please execute this command and attach its output to the ticket?

/usr/sbin/fping -C18 -p1000 -b32 -t1000 -i0 192.168.10.100
Comment by zabbix_1993 [ 2025 Jan 08 ]

Comment by Alexander Vladishev [ 2025 Jan 09 ]

Please also attach a fragment of the debug log for the "icmp pinger" process at the moment this IP address is being processed (approximately 100 lines of the log after the mention of this address and 25 lines before). You can increase the logging level at runtime using the option -R log_level_increase='icmp pinger'.

zabbix_server -c <path to zabbix_server.conf> -R log_level_increase='icmp pinger'
Comment by zabbix_1993 [ 2025 Jan 09 ]

zabbix-server.log

Comment by Alexander Vladishev [ 2025 Jan 09 ]

Judging by the log file, your IP address is unreachable from the machine where the Zabbix server is running. Did you execute the command I requested in the first comment on the different machine?

106110:20250109:171051.521 In line_process() linebuf: "192.168.100.10 : [11], timed out (NaN avg, 100% loss)"
Comment by zabbix_1993 [ 2025 Jan 09 ]

我在相同的测试环境中执行相同的操作,并得到相同的结果。
环境:Ubuntu 22.04; Zabbix 7.2.2 版本

Comment by Alexander Vladishev [ 2025 Jan 09 ]

Could you please execute this command as the user under which the zabbix_server process is running?

Comment by zabbix_1993 [ 2025 Jan 09 ]

Why is that?

Comment by zabbix_1993 [ 2025 Jan 10 ]

您好,我需要怎么做可以解决这个问题

Comment by Alexander Vladishev [ 2025 Jan 10 ]

I found a mention online that fping version 5.1 has this issue. Try updating this utility if you are using this specific version.

https://groups.google.com/g/fping-users/c/ord2CS9NG1I

Comment by dimir [ 2025 Jan 10 ]

User zabbix has probably no capabilities to use fping.

Comment by zabbix_1993 [ 2025 Jan 10 ]

我的fping版本是5.1,我在想办法更新版本

(My fping version is 5.1, I am trying to update the version)

Comment by zabbix_1993 [ 2025 Jan 10 ]

我的zabbix7.0升级7.2.2之前,fping版本也是5.1,使用正常

(Before my zabbix7.0 was upgraded to 7.2.2, the fping version was also 5.1, and it worked normally.)

Comment by zabbix_1993 [ 2025 Jan 10 ]

Comment by dimir [ 2025 Jan 10 ]

Please, this is an international issue tracker and the language is English, respect all the users. Added translation in parentheses.

Comment by Edgar Akhmetshin [ 2025 Jan 13 ]
setcap cap_net_raw+ep /usr/sbin/fping

Mostly case is a duplicate for ZBX-22833.

Comment by Alexander Vladishev [ 2025 Jan 13 ]

In the changelog of the fping utility version 5.2, there was a fix related to its operation as an unprivileged user. This might be connected to the described issue.

Fix running in unprivileged mode (#248, thanks @sfan5)

Generated at Sun Apr 27 01:37:13 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.