Failed upgrade 5.5 to 10.3
Hi - I upgraded from mysql 5.1 to MariaDB 5.5 That went perfectly fine.
I then tried upgrading from 5.5 to 10, and the install went okay but the database refuses to start. I tried various paths (mysql 5.1-mysql5.5-mariadb5.5-maria10) but the result is always the same:
Obviously the problem is '2018-10-14 19:45:57 0 [ERROR] InnoDB: Table `mysql`.`innodb_table_stats` not found.' from the log below
BUT - if I create this file in mariadb5.5 it then complains about the structure.
Is the a 5.5 compatible version of this table of this table that will work with 10.3?
<log> 2018-10-14 19:45:57 0 [Note] InnoDB: New log files created, LSN=3454638526081 2018-10-14 19:45:57 0 [Note] InnoDB: Creating tablespace and datafile system tables. 2018-10-14 19:45:57 0 [ERROR] InnoDB: Table `mysql`.`innodb_table_stats` not found. 2018-10-14 19:45:57 0x7fd641f657e0 InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.3.10/storage/innobase/pars/pars0pars.cc line 818 InnoDB: Failing assertion: sym_node->table != NULL InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to https://jira.mariadb.org/ InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: https://mariadb.com/kb/en/library/xtradbinnodb-recovery-modes/ InnoDB: about forcing recovery. 181014 19:45:57 [ERROR] mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware.
To report this bug, see https://mariadb.com/kb/en/reporting-bugs
We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail.
Server version: 10.3.10-MariaDB-log key_buffer_size=33554432 read_buffer_size=2097152 max_used_connections=0 max_threads=2502 thread_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 25709168 K bytes of memory Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0x0 thread_stack 0x30000 /usr/sbin/mysqld(my_print_stacktrace+0x2b)[0x55d6f488d5db] /usr/sbin/mysqld(handle_fatal_signal+0x537)[0x55d6f4378347] /lib64/libpthread.so.0(+0x3eba60f7e0)[0x7fd641b507e0] /lib64/libc.so.6(gsignal+0x35)[0x7fd6401aa4f5] /lib64/libc.so.6(abort+0x175)[0x7fd6401abcd5] ut/ut0rbt.cc:461(rbt_eject_node)[0x55d6f40e5b99] pars/pars0pars.cc:805(pars_retrieve_table_def)[0x55d6f45a4238] innobase/pars0grm.y:438(yyparse())[0x55d6f477320a] pars/pars0pars.cc:2138(pars_sql(pars_info_t*, char const*))[0x55d6f45a562d] que/que0que.cc:1212(que_eval_sql(pars_info_t*, char const*, unsigned long, trx_t*))[0x55d6f45a987e] row/row0mysql.cc:3840(row_drop_table_for_mysql(char const*, trx_t*, enum_sql_command, bool, bool))[0x55d6f45e0d25] row/row0mysql.cc:2886(row_mysql_drop_garbage_tables())[0x55d6f45e30e3] log/log0recv.cc:3691(recv_recovery_rollback_active())[0x55d6f456cb8e] srv/srv0start.cc:2337(srv_start(bool))[0x55d6f461eb1a] handler/ha_innodb.cc:4254(innodb_init)[0x55d6f4523760] sql/handler.cc:523(ha_initialize_handlerton(st_plugin_int*))[0x55d6f437ac78] sql/sql_plugin.cc:1432(plugin_initialize)[0x55d6f41cf531] sql/sql_plugin.cc:1714(plugin_init(int*, char, int))[0x55d6f41d04ca] sql/mysqld.cc:5375(init_server_components)[0x55d6f410c8dd] sql/mysqld.cc:5987(mysqld_main(int, char))[0x55d6f4110103] /lib64/libc.so.6(libc_start_main+0x100)[0x7fd640196d20] /usr/sbin/mysqld(+0x544859)[0x55d6f4104859] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash.
Answer Answered by Ian Gilfillan in this comment.
It looks like you didn't run mysql_upgrade. Carefully follow the steps at