Centos7 x64, zabbix 2.4.8

Looks like server was restarted mid-upgrade (server has just started and current DB version is 02050029). Was it killed like in ZBX-11203? Can you show more log?

14292:20160926:062104.030 Starting Zabbix Server. Zabbix 3.0.4 (revision 61185).
14292:20160926:062104.030 ****** Enabled features ******
14292:20160926:062104.030 SNMP monitoring: YES
14292:20160926:062104.030 IPMI monitoring: YES
14292:20160926:062104.030 Web monitoring: YES
14292:20160926:062104.030 VMware monitoring: YES
14292:20160926:062104.030 SMTP authentication: YES
14292:20160926:062104.030 Jabber notifications: YES
14292:20160926:062104.030 Ez Texting notifications: YES
14292:20160926:062104.030 ODBC: YES
14292:20160926:062104.030 SSH2 support: YES
14292:20160926:062104.030 IPv6 support: YES
14292:20160926:062104.030 TLS support: YES
14292:20160926:062104.030 ******************************
14292:20160926:062104.030 using configuration file: /etc/zabbix/zabbix_server.conf
14292:20160926:062104.037 current database version (mandatory/optional): 02050029/02050029
14292:20160926:062104.037 required mandatory version: 03000000
14292:20160926:062104.037 starting automatic database upgrade
14292:20160926:062104.037 [Z3005] query failed: [1050] Table 'application_prototype' already exists [create table application_prototype (
application_prototypeid bigint unsigned not null,
itemid bigint unsigned not null,
templateid bigint unsigned,
name varchar(255) default '' not null,
primary key (application_prototypeid)
) engine=innodb]
14292:20160926:062104.037 database upgrade failed
14301:20160926:062114.275 Starting Zabbix Server. Zabbix 3.0.4 (revision 61185).
14301:20160926:062114.275 ****** Enabled features ******
14301:20160926:062114.275 SNMP monitoring: YES
14301:20160926:062114.275 IPMI monitoring: YES
14301:20160926:062114.275 Web monitoring: YES
14301:20160926:062114.275 VMware monitoring: YES
14301:20160926:062114.275 SMTP authentication: YES
14301:20160926:062114.275 Jabber notifications: YES
14301:20160926:062114.275 Ez Texting notifications: YES
14301:20160926:062114.275 ODBC: YES
14301:20160926:062114.275 SSH2 support: YES
14301:20160926:062114.275 IPv6 support: YES
14301:20160926:062114.275 TLS support: YES
14301:20160926:062114.275 ******************************
14301:20160926:062114.275 using configuration file: /etc/zabbix/zabbix_server.conf
14301:20160926:062114.279 current database version (mandatory/optional): 02050029/02050029
14301:20160926:062114.279 required mandatory version: 03000000
14301:20160926:062114.279 starting automatic database upgrade
14301:20160926:062114.279 [Z3005] query failed: [1050] Table 'application_prototype' already exists [create table application_prototype (
application_prototypeid bigint unsigned not null,
itemid bigint unsigned not null,
templateid bigint unsigned,
name varchar(255) default '' not null,
primary key (application_prototypeid)
) engine=innodb]
14301:20160926:062114.279 database upgrade failed

I'm more interested in what was before the errors started.

See log in attach.

I my second try upgrade zabbix from 2.4.x to 3.x First one been and june.

Is it a vanilla Zabbix database?

Sorry, but I'm not understand what mean when wrote "vanilla"

Have you modified database schema? Where did application_prototype table come from? Please show the output of describe application_prototype;

I can give you dump? I was use in 2.4.8 only imap plugin.
I have dump from 2.4.8 Attach it to you?

Hi, maybe I can help you with this. I had the same problem and actually was really silly. What I've done is that I installed a new and fresh Zabbix instance in a new server and use the mysql templates that came within /usr/share/doc/zabbix-server-mysql/create.sql.gz. After that I took the MySQL dump that I did from the OLD Zabbix Server and loaded in this new server. Then when I started the zabbix-server service I've got the same error that you have reported. If you notice the error and compare the OLD tables with the new tables, the 'application_prototype' doesn't exist (and many others) but it is created by the create.sql.gz templates.

If you did the same thing all that you have to do is to DROP de zabbix database, create it again and load the OLD dump, then start the service. You should not load the create.sql.gz templates.

Hope this could be usefull to you.

Closing an old issue as Workaround proposed as per the last comment.