Comments - Failed upgrade 5.5 to 10.3
Content reproduced on this site is the property of its respective owners,
and this content is not reviewed in advance by MariaDB. The views, information and opinions
expressed by this content do not necessarily represent those of MariaDB or any other party.
Hi Ian - thanks for the reply. Problem is I cannot run mysql_upgrade because the server won't even start. I did get past the innodb_xxx table structure issues but it would still not start up. I did note though that I didn't set innodb_fast_shutdown to 0. What's odd is that in the test server this went without a hitch - but the data volumes are vastly different
Current failure log is;
2018-10-15 19:24:11 0 [Note] Using unique option prefix 'myisam_recover' is error-prone and can break in the future. Please use the full name 'myisam-recover-options' instead. 2018-10-15 19:24:11 0 [Note] InnoDB: Using Linux native AIO 2018-10-15 19:24:11 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2018-10-15 19:24:11 0 [Note] InnoDB: Uses event mutexes 2018-10-15 19:24:11 0 [Note] InnoDB: Compressed tables use zlib 1.2.3 2018-10-15 19:24:11 0 [Note] InnoDB: Number of pools: 1 2018-10-15 19:24:11 0 [Note] InnoDB: Using SSE2 crc32 instructions 2018-10-15 19:24:11 0 [Note] InnoDB: Initializing buffer pool, total size = 12G, instances = 8, chunk size = 128M 2018-10-15 19:24:11 0 [Note] InnoDB: Completed initialization of buffer pool 2018-10-15 19:24:12 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2018-10-15 19:24:12 0 [Note] InnoDB: Upgrading redo log: 3*268435456 bytes; LSN=3455893686413 2018-10-15 19:24:12 0 [Note] InnoDB: Starting to delete and rewrite log files. 2018-10-15 19:24:12 0 [Note] InnoDB: Setting log file ./ib_logfile101 size to 268435456 bytes 2018-10-15 19:24:12 0 [Note] InnoDB: Setting log file ./ib_logfile1 size to 268435456 bytes 2018-10-15 19:24:12 0 [Note] InnoDB: Setting log file ./ib_logfile2 size to 268435456 bytes 2018-10-15 19:24:12 0 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0 2018-10-15 19:24:12 0 [Note] InnoDB: New log files created, LSN=3455893686413 2018-10-15 19:24:12 0 [Note] InnoDB: Creating tablespace and datafile system tables. 2018-10-15 19:24:12 0 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name. Please run mysql_upgrade 2018-10-15 19:24:12 0 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name. Please run mysql_upgrade 2018-10-15 19:24:12 0 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name. Please run mysql_upgrade 2018-10-15 19:24:12 0 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name. Please run mysql_upgrade 2018-10-15 19:24:12 0x7fa44e23f7e0 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. 181015 19:24:12 [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 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)[0x560bad8c35db] mysys/stacktrace.c:270(my_print_stacktrace)[0x560bad3ae347] /lib64/libpthread.so.0(+0x3eba60f7e0)[0x7fa44de2a7e0] /lib64/libc.so.6(gsignal+0x35)[0x7fa44c4844f5] /lib64/libc.so.6(abort+0x175)[0x7fa44c485cd5] ut/ut0rbt.cc:461(rbt_eject_node)[0x560bad11bb99] pars/pars0pars.cc:805(pars_retrieve_table_def)[0x560bad5da238] innobase/pars0grm.y:438(yyparse())[0x560bad7a920a] pars/pars0pars.cc:2138(pars_sql(pars_info_t*, char const*))[0x560bad5db62d] que/que0que.cc:1212(que_eval_sql(pars_info_t*, char const*, unsigned long, trx_t*))[0x560bad5df87e] row/row0mysql.cc:3840(row_drop_table_for_mysql(char const*, trx_t*, enum_sql_command, bool, bool))[0x560bad616d25] row/row0mysql.cc:2886(row_mysql_drop_garbage_tables())[0x560bad6190e3] log/log0recv.cc:3691(recv_recovery_rollback_active())[0x560bad5a2b8e] srv/srv0start.cc:2337(srv_start(bool))[0x560bad654b1a] handler/ha_innodb.cc:4254(innodb_init)[0x560bad559760] sql/handler.cc:523(ha_initialize_handlerton(st_plugin_int*))[0x560bad3b0c78] sql/sql_plugin.cc:1432(plugin_initialize)[0x560bad205531] sql/sql_plugin.cc:1714(plugin_init(int*, char, int))[0x560bad2064ca] sql/mysqld.cc:5375(init_server_components)[0x560bad1428dd] sql/mysqld.cc:5987(mysqld_main(int, char))[0x560bad146103] /lib64/libc.so.6(libc_start_main+0x100)[0x7fa44c470d20] /usr/sbin/mysqld(+0x544859)[0x560bad13a859] 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.