Need help Zabbix 1.8.8 - killing itself

[ataylo13]

How do I turn off the "feature" for detecting duplicate hosts. I upgraded from 1.8.3 to 1.8.8 last night, and now every so often the zabbix_server process decides to kill itself saying:
23166:20111013:093030.694 Error: duplicate hosts [hostnamexxx] found. Exiting...
23136:20111013:093030.704 One child process died (PID:23166,exitcode/signal:255). Exiting ...

When I search the database I am not finding a duplicate. Alerting and disabling a host is acceptable, but tanking the whole server is a horrible "feature" for production monitoring servers.

Any help would be greatly appreciated.

[simon123]

Similar issue

How do I turn off the "feature" for detecting duplicate hosts. I upgraded from 1.8.3 to 1.8.8 last night, and now every so often the zabbix_server process decides to kill itself saying:
23166:20111013:093030.694 Error: duplicate hosts [hostnamexxx] found. Exiting...
23136:20111013:093030.704 One child process died (PID:23166,exitcode/signal:255). Exiting ...

When I search the database I am not finding a duplicate. Alerting and disabling a host is acceptable, but tanking the whole server is a horrible "feature" for production monitoring servers.

Any help would be greatly appreciated.

I bumped into the same issue when developing some API functionality.
After adding a host trough API, then deleting it in GUI, then adding it shortly after that with the API again, gave me this error. I just made sure that there where no duplicates and then rebooted zabbix_server and all was well.

I don't know how exactly i produced this error. As i said earlier this was on a development machine. (in a DM setup). I would also like to see this issue fully solved. the thought of Zabbix just killing itself on finding a duplicate host isn't really reassuring.

[mxa]

I saw info abouth it in http://www.zabbix.com/documentation/...n_and_upgrade:

3.3.5 For version 1.8.8
In some cases hosts and proxies with identical name might have appeared in the Zabbix database. Starting with 1.8.8, Zabbix server will shut down if it detects such a situation.

I'm also working in DM, and today I wanted to start upgrading test enviroment. Now I'm very worried. I didn't find any bug report in Jira regarding this. Did you report it?
I can risk to update to 1.8.8 if zabbix server killing itself.

[ataylo13]

I have not put in a bug report because I am hoping to hear why the developer thought it was a good idea.

@mxa: I am extremely paranoid about my production zabbix servers right now. I am monitoring over 3,500 servers and they are constantly being built and decommed. In the last week the zabbix server has gone down because of duplicates 3-4 times.

[mxa]

And that is why I thing that is a bug, but You are right: maybe we do not understand mechanism of checking for duplicate..
In DM, master node keep config for all childs hosts, so how duplicated host are checked? Which filds are consider as duplicated?, in DM only hostid is uniqe.
In one node range IP or DNS was alvays possible to duplicate, duplicating of "host" string was not allowed if you use frontend.. so..
Is it possible that someone with admin privileges is adding to database duplicated HOST? I thing that you excluded this posibbility.

I using Zabbix in the similar scale as You, at this point it is a upgrade blocker for me. I can't have situation that zabbix server may stopped itself because some silly duplicate (if there is any duplicate)
So lets hope that one of developers will interest of this thred...