[ZBX-11799] Auto Registration duplicates hosts Created: 2017 Feb 10 Updated: 2018 Dec 14 Resolved: 2018 Dec 14 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Agent (G), Server (S) |
Affects Version/s: | 3.2.2 |
Fix Version/s: | None |
Type: | Incident report | Priority: | Major |
Reporter: | Grzegorz Grabowski | Assignee: | Zabbix Development Team |
Resolution: | Won't fix | Votes: | 1 |
Labels: | agent, autoregistration, duplicates, server | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
Centos 7, Maria DB 10 |
Attachments: | error-1.png error-2.png |
Description |
Sometimes, when Agent reports to Zabbix Server first time, it did it with few, very quick probes: 58492:20170209:131038.642 cannot send list of active checks to "10.163.181.224": host [s-vmrh-esm-connector7] not found I don't know why Agents do that. Then, Zabbix Server registers 4 (or any other amount depends how many times Agent reports to) the same host, with the same HOST.HOST which is generally not possible. Bests, |
Comments |
Comment by Glebs Ivanovskis (Inactive) [ 2017 Feb 10 ] |
Is proxy involved in the process? Or maybe there are several agents? Log file timestamps look too close together. Active agent should not send requests that often. May be related to ZBX-4973. |
Comment by Oleksii Zagorskyi [ 2017 Feb 10 ] |
ZBX-4134 is related too. |
Comment by Grzegorz Grabowski [ 2017 Feb 10 ] |
No proxy involves and I don't know if there is more than one agent on this host. |
Comment by Alexander Vladishev [ 2017 Feb 10 ] |
Please check ServerActive option in the configuration file of Zabbix agent. How many times the IP address of the server is specified in it? |
Comment by Grzegorz Grabowski [ 2017 Feb 14 ] |
I checked it. Bests, |
Comment by Alexander Vladishev [ 2018 May 08 ] |
ServerActive with multiple ip addresses can be used for multiple Zabbix servers or proxies. Pointing to the same server produces several requests in one time. Please see documentation for more details. |