[ZBX-9706] Host duplicate with autoregistration rules Created: 2015 Jul 15  Updated: 2018 Mar 06  Resolved: 2018 Mar 06

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Server (S)
Affects Version/s: 2.4.5
Fix Version/s: None

Type: Incident report Priority: Trivial
Reporter: Vladimir Assignee: Unassigned
Resolution: Unsupported version Votes: 0
Labels: autoregistration, duplicates
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

We use zabbix server 2.4.5 and zabbix agent 2.4.5. OS is centos 6
We use auto registration action for new zabbix agent. Sometimes we have duplicate host. The hosts has the same ip, names and different id in table hosts.
For registration we use metadata.



 Comments   
Comment by richlv [ 2015 Jul 15 ]

could you please show entries of such identical hosts from the database ?

Comment by Vladimir [ 2015 Jul 15 ]

hostid: 567125
proxy_hostid: NULL
host: ds002.stolplit.ru
status: 0
disable_until: 0
error:
available: 1
errors_from: 0
lastaccess: 0
ipmi_authtype: 0
ipmi_privilege: 2
ipmi_username:
ipmi_password:
ipmi_disable_until: 0
ipmi_available: 0
snmp_disable_until: 0
snmp_available: 0
maintenanceid: NULL
maintenance_status: 0
maintenance_type: 0
maintenance_from: 0
ipmi_errors_from: 0
snmp_errors_from: 0
ipmi_error:
snmp_error:
jmx_disable_until: 0
jmx_available: 0
jmx_errors_from: 0
jmx_error:
name: ds002.stolplit.ru
flags: 0
templateid: NULL
description:

hostid: 567127
proxy_hostid: NULL
host: ds002.stolplit.ru
status: 0
disable_until: 0
error:
available: 1
errors_from: 0
lastaccess: 0
ipmi_authtype: 0
ipmi_privilege: 2
ipmi_username:
ipmi_password:
ipmi_disable_until: 0
ipmi_available: 0
snmp_disable_until: 0
snmp_available: 0
maintenanceid: NULL
maintenance_status: 0
maintenance_type: 0
maintenance_from: 0
ipmi_errors_from: 0
snmp_errors_from: 0
ipmi_error:
snmp_error:
jmx_disable_until: 0
jmx_available: 0
jmx_errors_from: 0
jmx_error:
name: ds002.stolplit.ru
flags: 0
templateid: NULL
description:

Generated at Thu Mar 28 19:08:41 EET 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.