discover process adds windows host that doesn't exist anymore

[xanadu]

I have an issue that my discover process adds a Windows server host that is not present anymore. The host was deleted 3 weeks ago. Every time I delete the host IP from the Hosts view it reappears on the next discover schedule.
Any ideas? I have this issue at two different customers. One is running v3.0.6, the other v3.2.2

The discover process has 2 checks:

ICMP ping and Zabbix agent "system.uname"

You cannot ping the ip address, so it's unclear to me why the host ip adress is added everytime again.

[xanadu]

I still have the same issue. Now running Zabbix v3.2.3.

This is my discovery rule.



It is discovering ip 10.81.2.18 but this is not an active device. I cannot ping it and it also states the zabbix agent is down:



This IP has been used previously but is not used anymore for over 2 months.

Anyone?

[xanadu]

Still have this issue for multiple retired vm's

[louis-m]

Did you get this resolved? I've got the same issue and as much as I delete them, they return even though they don't exist.

[xanadu]

No I haven't, I turned of the discovery to avoid this.

[pedropilla]

I'm using 3.4.4 and having this issue too, I even removed the ICMP and based the discovery on a SNMP get item but remains discovering hosts that doesnt exist.

[clevelas]

I know this is an old thread, so maybe a bump? I'm seeing this issues still on 5.0 (it was happening on the original 4.4 version I started with and continues with 5.0.3). Using SNMP discovery and nothing exists on the IP address. I've got about six hosts now that are no longer on the network. I remove them from zabbix, but they keep showing up as if they were newly discovered (and get put in the same groups as their original discovery).

[jirk]

Hello
The same situation as above. In my case database partitioned according to this link https://bestmonitoringtools.com/zabb...ysql-database/ Where could be problem? Thanks