Description:
190607 12:10:28 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data
2019-06-07 12:10:29 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-06-07 12:10:29 0 [Note] /usr/local/mysql/bin/mysqld (mysqld 5.6.24) starting as process 2133 ...
2019-06-07 12:10:29 2133 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/mysql/data/ is case insensitive
2019-06-07 12:10:29 2133 [Note] Plugin 'FEDERATED' is disabled.
2019-06-07 12:10:29 2133 [Note] InnoDB: Using atomics to ref count buffer pool pages
2019-06-07 12:10:29 2133 [Note] InnoDB: The InnoDB memory heap is disabled
2019-06-07 12:10:29 2133 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-06-07 12:10:29 2133 [Note] InnoDB: Memory barrier is not used
2019-06-07 12:10:29 2133 [Note] InnoDB: Compressed tables use zlib 1.2.3
2019-06-07 12:10:29 2133 [Note] InnoDB: Using CPU crc32 instructions
2019-06-07 12:10:29 2133 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2019-06-07 12:10:29 2133 [Note] InnoDB: Completed initialization of buffer pool
2019-06-07 12:10:29 2133 [Note] InnoDB: Highest supported file format is Barracuda.
2019-06-07 12:10:29 2133 [Note] InnoDB: 128 rollback segment(s) are active.
2019-06-07 12:10:29 2133 [Note] InnoDB: Waiting for purge to start
InnoDB: Error: tablespace id is 10505 in the data dictionary
InnoDB: but in file ./dev/global_tax_info.ibd it is 12310!
2019-06-07 12:10:29 7000007ab000 InnoDB: Assertion failure in thread 123145310351360 in file fil0fil.cc line 796
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/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
06:40:29 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.
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.
key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
How to repeat:
190607 12:10:28 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data
2019-06-07 12:10:29 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-06-07 12:10:29 0 [Note] /usr/local/mysql/bin/mysqld (mysqld 5.6.24) starting as process 2133 ...
2019-06-07 12:10:29 2133 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/mysql/data/ is case insensitive
2019-06-07 12:10:29 2133 [Note] Plugin 'FEDERATED' is disabled.
2019-06-07 12:10:29 2133 [Note] InnoDB: Using atomics to ref count buffer pool pages
2019-06-07 12:10:29 2133 [Note] InnoDB: The InnoDB memory heap is disabled
2019-06-07 12:10:29 2133 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-06-07 12:10:29 2133 [Note] InnoDB: Memory barrier is not used
2019-06-07 12:10:29 2133 [Note] InnoDB: Compressed tables use zlib 1.2.3
2019-06-07 12:10:29 2133 [Note] InnoDB: Using CPU crc32 instructions
2019-06-07 12:10:29 2133 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2019-06-07 12:10:29 2133 [Note] InnoDB: Completed initialization of buffer pool
2019-06-07 12:10:29 2133 [Note] InnoDB: Highest supported file format is Barracuda.
2019-06-07 12:10:29 2133 [Note] InnoDB: 128 rollback segment(s) are active.
2019-06-07 12:10:29 2133 [Note] InnoDB: Waiting for purge to start
InnoDB: Error: tablespace id is 10505 in the data dictionary
InnoDB: but in file ./dev/global_tax_info.ibd it is 12310!
2019-06-07 12:10:29 7000007ab000 InnoDB: Assertion failure in thread 123145310351360 in file fil0fil.cc line 796
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/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
06:40:29 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.
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.
key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
