Cannot Upgrade from MySQL 5.7.24-26 to 8.0.13-3
General
Escalation
General
Escalation
Description
Environment
None
Attachments
6
- 02 Jan 2019, 03:55 PM
- 02 Jan 2019, 03:55 PM
- 01 Jan 2019, 09:48 PM
- 01 Jan 2019, 09:47 PM
- 01 Jan 2019, 10:59 AM
- 28 Dec 2018, 11:59 PM
causes
is duplicated by
Smart Checklist
Activity
Show:

Laurynas Biveinis March 27, 2019 at 1:33 PM
This has caused

Olawale Jacob Adigun January 18, 2019 at 4:05 PM
Correction just found out it's released and available

Olawale Jacob Adigun January 18, 2019 at 4:01 PM
When will 8.0.13-4 version be released?

Lalit Choudhary January 18, 2019 at 9:38 AM
Tested Upgrade from 5.7.24 to 8.0.13-4, And it working fine now.
Mysql Logs : after running mysql_upgrade

Sergiu Hlihor January 18, 2019 at 3:05 AM
My instance also resumed and started successfully after upgrading from 8.0.13-3 to 8.0.13-4.
Done
Details
Assignee
Satya BodapatiSatya BodapatiReporter
Jonathan HorowitzJonathan HorowitzTime tracking
2d 3h 25m loggedFix versions
Affects versions
Priority
High
Details
Details
Assignee

Reporter

Time tracking
2d 3h 25m logged
Fix versions
Affects versions
Priority
Smart Checklist
Open Smart Checklist
Smart Checklist
Open Smart Checklist
Smart Checklist

Open Smart Checklist
Created December 27, 2018 at 8:57 PM
Updated March 6, 2024 at 12:30 PM
Resolved January 9, 2019 at 12:05 PM
2018-12-23T06:59:39.284742Z 2 [ERROR] [MY-013183] [InnoDB] Assertion failure: dict0dict.cc:1230:table2 == NULL thread 47400341178112 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. 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: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 06:59:39 UTC - 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. Attempting to collect some information that could help diagnose the problem. As this is a crash and something is definitely wrong, the information collection process might fail. Please help us make Percona Server better by reporting any bugs at https://bugs.percona.com/ key_buffer_size=33554432 read_buffer_size=2097152 max_used_connections=0 max_threads=16001 thread_count=1 connection_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)max_threads = 1962540456704 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x2b1c7fb404d0 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 = 2b1c407f7dc8 thread_stack 0x30000 /usr/local/mysql-prod/bin/mysqld(my_print_stacktrace(unsigned char, unsigned long)+0x2e) [0x2b1c3a3934ae] /usr/local/mysql-prod/bin/mysqld(handle_fatal_signal+0x4d1) [0x2b1c3975b341] /opt/glibc-2.19/lib/libpthread.so.0(+0xfb20) [0x2b1c3bfe6b20] /opt/glibc-2.19/lib/libc.so.6(gsignal+0x38) [0x2b1c3de45ac8] /opt/glibc-2.19/lib/libc.so.6(abort+0x148) [0x2b1c3de46e88] /usr/local/mysql-prod/bin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x2c7) [0x2b1c3a6d0177] /usr/local/mysql-prod/bin/mysqld(dict_table_add_to_cache(dict_table_t*, unsigned long, mem_block_info_t*)+0x318) [0x2b1c3a77f8b8] /usr/local/mysql-prod/bin/mysqld(+0x2016cf3) [0x2b1c3a7b1cf3] /usr/local/mysql-prod/bin/mysqld(dict_load_table(char const*, bool, dict_err_ignore_t)+0x777) [0x2b1c3a7b2897] /usr/local/mysql-prod/bin/mysqld(dict_table_open_on_name(char const*, unsigned long, unsigned long, dict_err_ignore_t)+0x160) [0x2b1c3a787000] /usr/local/mysql-prod/bin/mysqld(+0x2032684) [0x2b1c3a7cd684] /usr/local/mysql-prod/bin/mysqld(dd_upgrade_table(THD*, char const*, char const*, dd::Table*, TABLE*)+0xa2d) [0x2b1c3a7d25ad] /usr/local/mysql-prod/bin/mysqld(+0x1bb73c0) [0x2b1c3a3523c0] /usr/local/mysql-prod/bin/mysqld(dd::upgrade_57::migrate_all_frm_to_dd(THD*, char const*, bool)+0x4ef) [0x2b1c3a3538ff] /usr/local/mysql-prod/bin/mysqld(dd::upgrade_57::fill_dd_and_finalize(THD*)+0x17c) [0x2b1c3a34375c] /usr/local/mysql-prod/bin/mysqld(+0x106b26b) [0x2b1c3980626b] /usr/local/mysql-prod/bin/mysqld(+0x1c9e1af) [0x2b1c3a4391af] /opt/glibc-2.19/lib/libpthread.so.0(+0x7144) [0x2b1c3bfde144] /opt/glibc-2.19/lib/libc.so.6(clone+0x6d) [0x2b1c3defcc6d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0): is an invalid pointer Connection ID (thread ID): 2 Status: NOT_KILLED You may download the Percona Server operations manual by visiting http://www.percona.com/software/percona-server/. You may find information in the manual which will help you identify the cause of the crash.