Problem with deleted hosts after upgrade from 2.4.7 to 3.0.0

[mvazquez]

Hello all,

I'm experiencing an strange issue with deleted hosts after upgrading to 3.0.0.

In my Zabbix installation there is a discovery rule as follows:

Checks:
ICMP ping
SNMPv2 agent ".1.3.6.1.2.1.1.1.0"

Device uniqueness criteria
Ip address

It is intended to auto discover Linux boxes over our internal network. In conjunction with that, there is an Action rule that in case of receive a value like "Linux" from SNMP check, adds the server to an specific group and links it a template.

Zabbix 2.4.7:

If server doesn't reply to the snmp check or ping, it's not processed by the action rule.

Zabbix 3.0.0:

If server doesn't reply to the snmp check, but reply to ping it's processed by the action rule every time discovery rule runs (every hour).

This only happens with three different hosts, i've tried to:

Disable the host: It's marked as active automatically after discovery rule finish
Delete the host: It's auto-discovered and, therefore created again

-------------

Someone facing this issue?

[clayton940]

This seems to be a discovery issue. I have had this problem many times on 2.4.x I assume it's a carry over into 3.0 and what I had to do was truncate the dhosts and the dservices table and when the next discovery ran it went ok.

It seems that a lot of database related issues don't get addressed ie discovery issues and foreign key constraints.