-
Problem report
-
Resolution: Fixed
-
Major
-
5.0.29, 6.0.10, 6.2.4, 6.4.0beta3
-
Red Hat Enterprise Linux Server release 7.6
zabbix-proxy-pgsql-5.0.26-1.el7.x86_64
zabbix-get-5.0.26-1.el7.x86_64
zabbix-agent2-5.0.26-1.el7.x86_64
-
Support backlog
-
0.3
Steps to reproduce:
- A "net.tcp.port[183.3.224.149,443]" monitoring item is configured in the host.
- If IP address 183.3.224.149 is unreachable from the network, the agent cannot obtain data and the agent.ping alarm is triggered.However, using zabbix_get agent is available to obtain the value of other monitor items.
- zabbix client version
Result:
cat /var/log/zabbix/zabbix_proxy.log
50618:20221108:004304.928 Zabbix agent item "net.tcp.port[183.3.224.149,443]" on host "11.99.2.30" failed: first network error, wait for 15 seconds
50633:20221108:010454.893 resuming Zabbix agent checks on host "11.99.2.30": connection restored
50633:20221108:010524.896 Zabbix agent item "net.tcp.port[183.3.224.149,443]" on host "11.99.2.30" failed: first network error, wait for 15 seconds
50633:20221108:011454.939 resuming Zabbix agent checks on host "11.99.2.30": connection restored
50630:20221108:012625.828 Zabbix agent item "net.tcp.port[183.3.224.149,443]" on host "11.99.2.30" failed: first network error, wait for 15 seconds
50630:20221108:014655.946 resuming Zabbix agent checks on host "11.99.2.30": connection restored
Expected:
- is duplicated by
-
ZBX-19409 net.tcp.port in zabbix agent2 sending ZBX_NOTSUPPORTED and not respecting configuration timeout
- Closed