[ZBX-25899] Monitoring issues with IPv6 when IPv4 is not available Created: 2025 Jan 17  Updated: 2025 Feb 17  Resolved: 2025 Feb 17

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Proxy (P), Server (S)
Affects Version/s: 7.0.8
Fix Version/s: 7.0.10rc1, 7.2.4rc1, 7.4.0alpha1

Type: Problem report Priority: Trivial
Reporter: Danilo G. Baio Assignee: Vladislavs Sokurenko
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: 16h
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by ZBX-26014 Zabbix passive agent checks fail rand... Closed
Team: Team A
Sprint: S25-W6/7
Story Points: 1

 Description   

Hi,

**

I have a mix of hosts/proxies with both IPv4 and IPv6, and some proxies running only on IPv6.

After upgrading from 6.X to 7.0.8, I noticed that many Zabbix agent hosts were unavailable, including hosts that are monitored by proxies and the server, which has both IPv4 and IPv6.

All hosts are configured with "DNS names". When I change them to "IP addresses" and insert their IPv6 addresses, they work again.

Steps to reproduce:

  1. Configure a proxy with IPv6 only and monitor an agent that has both IPv4 and IPv6.
  2. Configure the host to be monitored by its DNS name, which resolves both IPv4 and IPv6.

Result:

This is a log from an IPv6-only proxy that cannot connect to a host which has both IPv4 and IPv6:

75126:20250117:163846.857 In zbx_async_check_agent() key:'net.if.in[igb0]' host:'himawari.x.y.com' addr:'himawari.x.y.com'  conn:'TLS with PSK'
 75126:20250117:163846.857 In zbx_is_ip4() ip:'himawari.x.y.com'
 75126:20250117:163846.857 End of zbx_is_ip4():FAIL
 75126:20250117:163846.857 In zbx_is_ip6() ip:'himawari.x.y.com'
 75126:20250117:163846.857 End of zbx_is_ip6():FAIL
 75126:20250117:163846.857 In zbx_is_ip4() ip:'himawari.x.y.com'
 75126:20250117:163846.857 End of zbx_is_ip4():FAIL
 75126:20250117:163846.857 In zbx_is_ip6() ip:'himawari.x.y.com'
 75126:20250117:163846.857 End of zbx_is_ip6():FAIL
 75126:20250117:163846.857 End of zbx_async_check_agent():SUCCEED
 75126:20250117:163846.858 In agent_task_process() step 'init' event:0 itemid:43726 addr:210.231.Y.Z
 75126:20250117:163846.858 In zbx_is_ip4() ip:'210.231.Y.Z'
 75126:20250117:163846.858 End of zbx_is_ip4():SUCCEED
 75126:20250117:163846.858 In process_async_result() key:'system.users.num' host:'himawari.x.y.com' addr:'himawari.x.y.com'
 75126:20250117:163846.858 finished processing itemid:43726 processing:2
 75126:20250117:163846.858 End of process_async_result():NETWORK_ERROR
 75126:20250117:163846.858 End of async_event():stop
 75126:20250117:163846.858 End of async_dns_event()

Zabbix agent item "net.if.out[igb0]" on host "himawari.x.y.com" failed: first network error, wait for 15 seconds
...
temporarily disabling Zabbix agent checks on host "himawari.x.y.com": interface unavailable
 

Expected:

Zabbix agent working on IPv6 and DNS name.



 Comments   
Comment by Alexander Vladishev [ 2025 Feb 07 ]

A very similar issue is described in ZBX-26014.

Comment by Vladislavs Sokurenko [ 2025 Feb 10 ]

Implemented in pull request:

feature/ZBX-25899-7.2
feature/ZBX-25899-7.3

Comment by Vladislavs Sokurenko [ 2025 Feb 12 ]

Implemented in:

Comment by Andrii Fediuk [ 2025 Feb 13 ]

Updated documentation:

  • Passive and active agent checks: 7.0, 7.2, 7.4 (added a note describing the behavior of the agent poller).
  • Upgrade notes for 7.0.10: 7.0 (added a note describing the behavior of the agent poller).
  • Upgrade notes for 7.2.4: 7.2 (added a note describing the behavior of the agent poller).
Generated at Wed Apr 02 16:25:14 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.