2019-01-07T16:52:24.611119Z 0 [ERROR] [MY-010901] [Server] Can't open shared library '/usr/lib64/mysql/plugin/query_response_time.so' (errno: 0 /usr/lib64/mysql/plugin/query_response_time.so: cannot open shared object file: No such file or directory). 2019-01-07T16:52:24.611213Z 0 [Warning] [MY-010736] [Server] Couldn't load plugin named 'QUERY_RESPONSE_TIME' with soname 'query_response_time.so'. 2019-01-07T16:52:24.611272Z 0 [ERROR] [MY-010901] [Server] Can't open shared library '/usr/lib64/mysql/plugin/query_response_time.so' (errno: 0 /usr/lib64/mysql/plugin/query_response_time.so: cannot open shared object file: No such file or directory). 2019-01-07T16:52:24.611291Z 0 [Warning] [MY-010736] [Server] Couldn't load plugin named 'QUERY_RESPONSE_TIME_AUDIT' with soname 'query_response_time.so'. 2019-01-07T16:52:24.611326Z 0 [ERROR] [MY-010901] [Server] Can't open shared library '/usr/lib64/mysql/plugin/query_response_time.so' (errno: 0 /usr/lib64/mysql/plugin/query_response_time.so: cannot open shared object file: No such file or directory). 2019-01-07T16:52:24.611354Z 0 [Warning] [MY-010736] [Server] Couldn't load plugin named 'QUERY_RESPONSE_TIME_READ' with soname 'query_response_time.so'. 2019-01-07T16:52:24.611387Z 0 [ERROR] [MY-010901] [Server] Can't open shared library '/usr/lib64/mysql/plugin/query_response_time.so' (errno: 0 /usr/lib64/mysql/plugin/query_response_time.so: cannot open shared object file: No such file or directory). 2019-01-07T16:52:24.611402Z 0 [Warning] [MY-010736] [Server] Couldn't load plugin named 'QUERY_RESPONSE_TIME_WRITE' with soname 'query_response_time.so'. 2019-01-07T16:52:31.697373Z 2 [ERROR] [MY-013183] [InnoDB] Assertion failure: dict0dict.cc:1230:table2 == NULL thread 140194037483264 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. 16:52:31 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=268435456 read_buffer_size=2097152 max_used_connections=0 max_threads=10000 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 = 493627459801 K bytes of memory Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x3c2c3f0 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 = 7f8177cdbca8 thread_stack 0x46000 /usr/sbin/mysqld(my_print_stacktrace(unsigned char*, unsigned long)+0x2e) [0x1be1afe] /usr/sbin/mysqld(handle_fatal_signal+0x423) [0xf3e6c3] /lib64/libpthread.so.0() [0x3688a0f7e0] /lib64/libc.so.6(gsignal+0x35) [0x36886324f5] /lib64/libc.so.6(abort+0x175) [0x3688633cd5] /usr/sbin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x2b3) [0x1f69873] /usr/sbin/mysqld(dict_table_add_to_cache(dict_table_t*, unsigned long, mem_block_info_t*)+0x320) [0x200fbe0] /usr/sbin/mysqld() [0x204422c] /usr/sbin/mysqld(dict_load_table(char const*, bool, dict_err_ignore_t)+0x87f) [0x204507f] /usr/sbin/mysqld(dict_table_open_on_name(char const*, unsigned long, unsigned long, dict_err_ignore_t)+0x158) [0x20165f8] /usr/sbin/mysqld(dd_upgrade_table(THD*, char const*, char const*, dd::Table*, TABLE*)+0xf1) [0x20620f1] /usr/sbin/mysqld() [0x1b9feb6] /usr/sbin/mysqld(dd::upgrade_57::migrate_all_frm_to_dd(THD*, char const*, bool)+0x6f1) [0x1ba17d1] /usr/sbin/mysqld(dd::upgrade_57::fill_dd_and_finalize(THD*)+0x1b2) [0x1b91d82] /usr/sbin/mysqld() [0xfe7e9e] /usr/sbin/mysqld() [0x1c889bf] /lib64/libpthread.so.0() [0x3688a07aa1] /lib64/libc.so.6(clone+0x6d) [0x36886e8c4d]
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.
Described behavior already reported in our bugs database. Therefore I am closing this report as a duplicate. Please subscribe for the original bug report to receive updates in time.
Initial errors in the error log are due to QRT plugin being still installed (while it is dropped from 8.0). It can be removed by booting server with --skip-grant-tables option and removing the plugin manually:
mysql> select * from mysql.plugin;
+---------------------------+------------------------+
| name | dl |
+---------------------------+------------------------+
| QUERY_RESPONSE_TIME | query_response_time.so |
| QUERY_RESPONSE_TIME_AUDIT | query_response_time.so |
| QUERY_RESPONSE_TIME_READ | query_response_time.so |
| QUERY_RESPONSE_TIME_WRITE | query_response_time.so |
+---------------------------+------------------------+
4 rows in set (0.00 sec)
mysql> delete from mysql.plugin where dl='query_response_time.so';
Query OK, 4 rows affected (0.06 sec)
In place upgrade failed to start:
2019-01-07T16:52:24.611119Z 0 [ERROR] [MY-010901] [Server] Can't open shared library '/usr/lib64/mysql/plugin/query_response_time.so' (errno: 0 /usr/lib64/mysql/plugin/query_response_time.so: cannot open shared object file: No such file or directory).
2019-01-07T16:52:24.611213Z 0 [Warning] [MY-010736] [Server] Couldn't load plugin named 'QUERY_RESPONSE_TIME' with soname 'query_response_time.so'.
2019-01-07T16:52:24.611272Z 0 [ERROR] [MY-010901] [Server] Can't open shared library '/usr/lib64/mysql/plugin/query_response_time.so' (errno: 0 /usr/lib64/mysql/plugin/query_response_time.so: cannot open shared object file: No such file or directory).
2019-01-07T16:52:24.611291Z 0 [Warning] [MY-010736] [Server] Couldn't load plugin named 'QUERY_RESPONSE_TIME_AUDIT' with soname 'query_response_time.so'.
2019-01-07T16:52:24.611326Z 0 [ERROR] [MY-010901] [Server] Can't open shared library '/usr/lib64/mysql/plugin/query_response_time.so' (errno: 0 /usr/lib64/mysql/plugin/query_response_time.so: cannot open shared object file: No such file or directory).
2019-01-07T16:52:24.611354Z 0 [Warning] [MY-010736] [Server] Couldn't load plugin named 'QUERY_RESPONSE_TIME_READ' with soname 'query_response_time.so'.
2019-01-07T16:52:24.611387Z 0 [ERROR] [MY-010901] [Server] Can't open shared library '/usr/lib64/mysql/plugin/query_response_time.so' (errno: 0 /usr/lib64/mysql/plugin/query_response_time.so: cannot open shared object file: No such file or directory).
2019-01-07T16:52:24.611402Z 0 [Warning] [MY-010736] [Server] Couldn't load plugin named 'QUERY_RESPONSE_TIME_WRITE' with soname 'query_response_time.so'.
2019-01-07T16:52:31.697373Z 2 [ERROR] [MY-013183] [InnoDB] Assertion failure: dict0dict.cc:1230:table2 == NULL thread 140194037483264
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.
16:52:31 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=268435456
read_buffer_size=2097152
max_used_connections=0
max_threads=10000
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 = 493627459801 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x3c2c3f0
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 = 7f8177cdbca8 thread_stack 0x46000
/usr/sbin/mysqld(my_print_stacktrace(unsigned char*, unsigned long)+0x2e) [0x1be1afe]
/usr/sbin/mysqld(handle_fatal_signal+0x423) [0xf3e6c3]
/lib64/libpthread.so.0() [0x3688a0f7e0]
/lib64/libc.so.6(gsignal+0x35) [0x36886324f5]
/lib64/libc.so.6(abort+0x175) [0x3688633cd5]
/usr/sbin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x2b3) [0x1f69873]
/usr/sbin/mysqld(dict_table_add_to_cache(dict_table_t*, unsigned long, mem_block_info_t*)+0x320) [0x200fbe0]
/usr/sbin/mysqld() [0x204422c]
/usr/sbin/mysqld(dict_load_table(char const*, bool, dict_err_ignore_t)+0x87f) [0x204507f]
/usr/sbin/mysqld(dict_table_open_on_name(char const*, unsigned long, unsigned long, dict_err_ignore_t)+0x158) [0x20165f8]
/usr/sbin/mysqld(dd_upgrade_table(THD*, char const*, char const*, dd::Table*, TABLE*)+0xf1) [0x20620f1]
/usr/sbin/mysqld() [0x1b9feb6]
/usr/sbin/mysqld(dd::upgrade_57::migrate_all_frm_to_dd(THD*, char const*, bool)+0x6f1) [0x1ba17d1]
/usr/sbin/mysqld(dd::upgrade_57::fill_dd_and_finalize(THD*)+0x1b2) [0x1b91d82]
/usr/sbin/mysqld() [0xfe7e9e]
/usr/sbin/mysqld() [0x1c889bf]
/lib64/libpthread.so.0() [0x3688a07aa1]
/lib64/libc.so.6(clone+0x6d) [0x36886e8c4d]
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.