-
Type:
Problem report
-
Resolution: Unresolved
-
Priority:
Trivial
-
None
-
Affects Version/s: 7.4.13, 7.4.14
-
Component/s: Agent2 (G), Proxy (P), Server (S)
-
None
-
Environment:Our Installation:
- Zabbix server: 7.4.14, HA cluster (2 nodes, active/standby), MySQL (zabbix/zabbix-server-mysql:7.4.14-alpine)
- Zabbix proxies: 7.4.14, 2 active proxies in a proxy group (zabbix/zabbix-proxy-mysql:7.4.14-alpine)
proxy group: `failover_delay=20s`, `min_online=1`
proxy buffer mode: disk
- Zabbix agents: agent2 7.4.14 (debian 13)
`ServerActive` lists both proxies of the group separated by ;
`Hostname=<fqdn>`, `HostMetadata` set
`RefreshActiveChecks` not set (default 5s)
- Auto-registration action: condition on host metadata, operations: add to host group, link templates, enable host
The behavior was observed on two independent, similar installations running 7.4.14.
We had not observed it on earlier versions, but we cannot exclude that it existed before and simply did not trigger.Our Installation: - Zabbix server: 7.4.14, HA cluster (2 nodes, active/standby), MySQL (zabbix/zabbix-server-mysql:7.4.14-alpine) - Zabbix proxies: 7.4.14, 2 active proxies in a proxy group (zabbix/zabbix-proxy-mysql:7.4.14-alpine) proxy group: `failover_delay=20s`, `min_online=1` proxy buffer mode: disk - Zabbix agents: agent2 7.4.14 (debian 13) `ServerActive` lists both proxies of the group separated by ; `Hostname=<fqdn>`, `HostMetadata` set `RefreshActiveChecks` not set (default 5s) - Auto-registration action: condition on host metadata, operations: add to host group, link templates, enable host The behavior was observed on two independent, similar installations running 7.4.14. We had not observed it on earlier versions, but we cannot exclude that it existed before and simply did not trigger.
After upgrading to Zabbix 7.4.14, newly auto-registered hosts are created twice:
two rows in the `hosts` table with the same `host` name but different `hostid`,
both monitored by the same proxy group.
The server generates two auto-registration events for the same `autoreg_hostid`, a few seconds apart, before the first event's action (host creation) has completed.
This looks like a race condition between event generation and asynchronous action processing.
Steps to reproduce:
- Configure a proxy group with 2 active proxies; configure agents to point to both proxies in `ServerActive`; enable an auto-registration action on host metadata.
Start a new agent (host unknown to Zabbix) so that it sends its first active
check / registration data.- Wait for auto-registration and check the list of hosts and the auto-registration events.
Reproduces intermittently (observed on ~1/3 of hosts in one test installation), consistent with a race condition
Result:
- Duplicate hosts: two rows in the `hosts` table with identical `host` name but different `hostid`, both with `monitored_by` = proxy group (same `proxy_groupid`, `proxyid` NULL).
Both appear in Data collection → Hosts. - Duplicate auto-registration events (`events`, source=2): two events referring to the same `autoreg_hostid`, 2 seconds apart, both with `value=1`.
Expected:
Only one host created per auto-registered host.