Autodiscovery is detecting nonexistent duplicate hosts

[UniLEDLS]

Apologies: I've crossposted in the hopes of getting more eyes on.

I have a bunch of manually added hosts in to my Zabbix, as well as autodiscovery rules that search various subnets across our network. However, Zabbix appears to be finding devices that no longer exist on a particular subnet, and adding them as duplicates.
Please see the screenshot:



Drive-Out_2 is the duplicate, and has not existed on the 172.16 network for about 6 months. I only re-enabled autodiscovery today, so why is it finding duplicate hosts that do not exist on the network anymore? Nothing is on that IP address.

I can delete the duplicates, but once the autodiscovery runs again, they reappear. And it doesn't appear to happen to all hosts.

[Hamardaban]

Are you writing about "network discovery"?
If the host was created as a result of the network discovery there are 2 ways to delete it. 1 - change the network range in the network discovery rules and 2 - delete "detection information" directly from the database.

[UniLEDLS]

Are you writing about "network discovery"?
If the host was created as a result of the network discovery there are 2 ways to delete it. 1 - change the network range in the network discovery rules and 2 - delete "detection information" directly from the database.

But why is network discovery "finding" and creating a host on an IP address that isn't being used by any host, let alone that one?
In the example above, Out-Drive_2 is supposedly on 172.16.22.194 according to Zabbix network discovery, but in actual fact it's on 172.17.54.162.

[Hamardaban]

I do not know how your network discovery is set up and what you did with it - turned on/off , deleted hosts , etc.
It doesn't matter.
Understand one thing - if the host was created during network discovery, it will be recreated when deleted because information about it is stored in the "discovery rule".
The host does arise not because it is detected again, but because it was detected once.

[UniLEDLS]

I do not know how your network discovery is set up and what you did with it - turned on/off , deleted hosts , etc.
It doesn't matter.
Understand one thing - if the host was created during network discovery, it will be recreated when deleted because information about it is stored in the "discovery rule".
The host does arise not because it is detected again, but because it was detected once.

In that case, would it be wise to clear the detection information from the database periodically, then? Or will that cause problems with hosts that are accurate?

[Hamardaban]

No problem - information about the detection is deleted, not about the host itself.

https://www.zabbix.com/forum/in-russian/463259-удалить-элемент-из-списка-discovery-или-обновить-весь-список

[UniLEDLS]

No problem - information about the detection is deleted, not about the host itself.

https://www.zabbix.com/forum/in-russ...-список

Thanks for that, unfortunately it doesn't seem to make a difference

MariaDB [zabbix]> delete from dhosts where dhostid not in (select distinct dhostid from dservices);
Query OK, 0 rows affected (0.009 sec)

​

[Hamardaban]

First, remove the ip from the «dservices» and then clear the «dhosts» table.

[UniLEDLS]

First, remove the ip from the «dservices» and then clear the «dhosts» table.

That's what I did in the end and watched it overnight. Seems to have worked beautifully, thank you.