Zabbix 2.1.3 release database update acting wierd !!!!

[vrtareg]

Hi

Just would like to let know that the Database upgrade in 2.1.3 is trying to drop non existing indexes without checking if they are even exist:

27008:20130829:172155.791 [Z3005] query failed: [1091] Can't DROP 'id'; check that column/key exists [drop index id on history_sync]
9595:20130829:172532.960 [Z3005] query failed: [1091] Can't DROP 'id'; check that column/key exists [drop index id on history_uint_sync]
11626:20130829:172604.270 [Z3005] query failed: [1091] Can't DROP 'id'; check that column/key exists [drop index id on history_str_sync]
13227:20130829:172632.990 [Z3005] query failed: [1091] Can't DROP 'id'; check that column/key exists [drop index id on proxy_history]
15150:20130829:172712.860 [Z3005] query failed: [1091] Can't DROP 'id'; check that column/key exists [drop index id on proxy_dhistory]
16528:20130829:172741.196 [Z3005] query failed: [1091] Can't DROP 'id'; check that column/key exists [drop index id on proxy_autoreg_host]

I managed to create that indexes to allow upgrade to pass ...

Regards,
Areg

[tchjts1]

Thanks for reporting that. I have pointed it out to Alexei.

[Alexei]

Just would like to let know that the Database upgrade in 2.1.3 is trying to drop non existing indexes without checking if they are even exist

What database you are running?

[Sasha]

What version of the MySQL server?

Please attach the initial scheme of your database (i.e. before an upgrade).

mysqldump -d dbname > dbname.dump

Thank you.

[Sasha]

The database Zabbix 2.0 shall contain these indexes. Probably you did in it the custom changes?

[vrtareg]

Hi All

I did not make any changes in DB.

The DB was running on version 2.0.6 initially (a copy of production system for testing) and after that I ran the 2.1.1 for testing and the upgrade went Ok:

4831:20130813:110511.307 Starting Zabbix Server. Zabbix 2.1.1 (revision 37125).
4831:20130813:110511.308 ****** Enabled features ******
4831:20130813:110511.308 SNMP monitoring: YES
4831:20130813:110511.309 IPMI monitoring: YES
4831:20130813:110511.309 WEB monitoring: YES
4831:20130813:110511.309 Jabber notifications: NO
4831:20130813:110511.309 Ez Texting notifications: YES
4831:20130813:110511.309 ODBC: NO
4831:20130813:110511.310 SSH2 support: NO
4831:20130813:110511.310 IPv6 support: NO
4831:20130813:110511.310 ******************************
4831:20130813:110511.310 using configuration file: /usr/local/zabbix/etc/zabbix_server.conf
4831:20130813:110511.429 current database version (mandatory/optional): 02010000/02010000
4831:20130813:110511.429 required mandatory version: 02010091
4831:20130813:110511.429 starting automatic database upgrade
4831:20130813:110511.429 completed 1% of database upgrade
4831:20130813:110511.430 completed 2% of database upgrade
4831:20130813:110511.430 completed 3% of database upgrade

.....

4831:20130813:110522.418 completed 96% of database upgrade
4831:20130813:110523.223 completed 97% of database upgrade
4831:20130813:110523.975 completed 98% of database upgrade
4831:20130813:110524.693 completed 100% of database upgrade
4831:20130813:110524.693 database upgrade fully completed

After that I jumped to the version 2.1.3 (as version 2.1.2 was broken, missing files in tarball archive) and got these messages in log after starting Zabbix Server:

4831:20130829:164405.658 Zabbix Server stopped. Zabbix 2.1.1 (revision 37125).
18341:20130829:171141.148 Starting Zabbix Server. Zabbix 2.1.3 (revision 38217).
18341:20130829:171141.148 ****** Enabled features ******
18341:20130829:171141.148 SNMP monitoring: YES
18341:20130829:171141.148 IPMI monitoring: YES
18341:20130829:171141.148 WEB monitoring: YES
18341:20130829:171141.148 Jabber notifications: NO
18341:20130829:171141.148 Ez Texting notifications: YES
18341:20130829:171141.148 ODBC: NO
18341:20130829:171141.148 SSH2 support: NO
18341:20130829:171141.148 IPv6 support: NO
18341:20130829:171141.148 ******************************
18341:20130829:171141.148 using configuration file: /usr/local/zabbix/etc/zabbix_server.conf
18341:20130829:171141.152 current database version (mandatory/optional): 02010091/02010091
18341:20130829:171141.153 required mandatory version: 02010101
18341:20130829:171141.153 starting automatic database upgrade
18341:20130829:171141.170 completed 10% of database upgrade
18341:20130829:171141.174 completed 20% of database upgrade
18341:20130829:171141.194 completed 30% of database upgrade
18341:20130829:171141.194 [Z3005] query failed: [1091] Can't DROP 'id'; check that column/key exists [drop index id on history_sync]
18341:20130829:171141.195 database upgrade failed

Regards,
Areg

[vrtareg]

Hi

Also would like to mention that first initial server was build based on 2.0.4 sources and so the database.

Regards,
Areg