Failure to upgrade to 3.4.6

[cylaer]

Hi everyone,

I'm trying to upgrade our zabbix from 3.2 to 3.4.6, but I'm getting the following error on zabbix_server.log

34609:20180207:100309.766 Starting Zabbix Server. Zabbix 3.4.6 (revision 76823).
34609:20180207:100309.766 ****** Enabled features ******
34609:20180207:100309.766 SNMP monitoring: YES
34609:20180207:100309.766 IPMI monitoring: YES
34609:20180207:100309.766 Web monitoring: YES
34609:20180207:100309.766 VMware monitoring: YES
34609:20180207:100309.766 SMTP authentication: YES
34609:20180207:100309.766 Jabber notifications: YES
34609:20180207:100309.766 Ez Texting notifications: YES
34609:20180207:100309.766 ODBC: YES
34609:20180207:100309.766 SSH2 support: YES
34609:20180207:100309.766 IPv6 support: YES
34609:20180207:100309.766 TLS support: YES
34609:20180207:100309.766 ******************************
34609:20180207:100309.766 using configuration file: /etc/zabbix/zabbix_server.conf
34609:20180207:100309.772 current database version (mandatory/optional): 03040000/03040002
34609:20180207:100309.772 required mandatory version: 03040000
34609:20180207:100309.772 optional patches were found
34609:20180207:100309.772 starting automatic database upgrade
34609:20180207:100309.773 [Z3005] query failed: [1091] Can't DROP 'sessions_1'; check that column/key exists [drop index sessions_1 on sessions]
34609:20180207:100309.773 database upgrade failed

After that it just starts all over again. Any suggestions?

[volter]

If you haven't manipulated your schema, this should be considered a bug.

However, there are two ways you can work around this:

- Create an index of that name, so Zabbix can drop it. The details of the index don't matter _at all_.
- Zabbix is keeping track of what changes it already has done to the schema. If you figure out where that is and what "number" the next step has, you can manipulate that instead