-
Incident report
-
Resolution: Won't fix
-
Blocker
-
None
-
3.4.2
-
Centos 7 x64
mysql Ver 14.14 Distrib 5.7.14-8, for Linux (x86_64) using 6.2
Normal Zabbix Upgrade Process from Sources
Compile and Link - OK
DB Upgrade works fine until error at 45%.
25983:20171011:190511.204 Starting Zabbix Server. Zabbix 3.4.2 (revision 72885).
25983:20171011:190511.204 ****** Enabled features ******
25983:20171011:190511.204 SNMP monitoring: YES
25983:20171011:190511.204 IPMI monitoring: NO
25983:20171011:190511.204 Web monitoring: YES
25983:20171011:190511.204 VMware monitoring: YES
25983:20171011:190511.204 SMTP authentication: YES
25983:20171011:190511.204 Jabber notifications: NO
25983:20171011:190511.204 Ez Texting notifications: YES
25983:20171011:190511.204 ODBC: NO
25983:20171011:190511.204 SSH2 support: YES
25983:20171011:190511.204 IPv6 support: YES
25983:20171011:190511.204 TLS support: NO
25983:20171011:190511.204 ******************************
25983:20171011:190511.204 using configuration file: /usr/local/etc/zabbix_server.conf
25983:20171011:190511.231 current database version (mandatory/optional): 02020000/02020001
25983:20171011:190511.231 required mandatory version: 03040000
25983:20171011:190511.231 optional patches were found
25983:20171011:190511.232 starting automatic database upgrade
25983:20171011:190511.233 completed 0% of database upgrade
25983:20171011:190512.260 completed 1% of database upgrade
25983:20171011:190513.902 completed 2% of database upgrade
25983:20171011:190515.827 completed 3% of database upgrade
...
25983:20171011:190932.204 completed 43% of database upgrade
25983:20171011:190932.304 completed 44% of database upgrade
25983:20171011:190932.339 completed 45% of database upgrade
25983:20171011:190932.343 [Z3005] query failed: [1091] Can't DROP 'history_log_2'; check that column/key exists [drop index history_log_2 on history_log]
25983:20171011:190932.344 database upgrade failed
- is duplicated by
-
-
- Closed
-