2017-09-16 22:47:02 140690098809600 [ERROR] Table test/t1 has a primary key in InnoDB data dictionary, but not in MySQL! Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
|
|
2017-09-16 22:47:02 140690098809600 [ERROR] InnoDB: Table test/t1 contains 2 indexes inside InnoDB, which is different from the number of indexes 1 defined in the MySQL Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
|
|
2017-09-16 22:47:02 140690098809600 [ERROR] InnoDB: Table test/t1 contains 2 indexes inside InnoDB, which is different from the number of indexes 1 defined in the MySQL Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
|
|
CURRENT_TEST: innodb.innodb-dict
|
CURRENT_TEST: innodb.innodb-fk
|
2017-09-16 22:47:02 140690098506496 [Note] /usr/local/mariadb-10.1.27-linux-x86_64/bin/mysqld: Normal shutdown
|
|
2017-09-16 22:47:02 140690098506496 [Note] Event Scheduler: Purging the queue. 0 events
|
2017-09-16 22:47:02 140689815889664 [Note] InnoDB: FTS optimize thread exiting.
|
2017-09-16 22:47:02 140690098506496 [Note] InnoDB: Starting shutdown...
|
2017-09-16 22:47:03 7ff4eb397700 InnoDB: Assertion failure in thread 140689895159552 in file os0file.cc line 5400
|
InnoDB: Failing assertion: slot != NULL
|
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.
|
170916 22:47:03 [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.1.27-MariaDB
|
key_buffer_size=1048576
|
read_buffer_size=131072
|
max_used_connections=1
|
max_threads=153
|
thread_count=0
|
It is possible that mysqld could use up to
|
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 62911 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 0x48400
|
/usr/local/mariadb-10.1.27-linux-x86_64/bin/mysqld(my_print_stacktrace+0x2e)[0x7ff4f813bd1e]
|
/usr/local/mariadb-10.1.27-linux-x86_64/bin/mysqld(handle_fatal_signal+0x305)[0x7ff4f7c5fa75]
|
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10330)[0x7ff4f6c2b330]
|
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x39)[0x7ff4f607bf39]
|
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7ff4f607f348]
|
/usr/local/mariadb-10.1.27-linux-x86_64/bin/mysqld(+0x879e83)[0x7ff4f7f16e83]
|
/usr/local/mariadb-10.1.27-linux-x86_64/bin/mysqld(+0x9be61c)[0x7ff4f805b61c]
|
/usr/local/mariadb-10.1.27-linux-x86_64/bin/mysqld(+0x8ef330)[0x7ff4f7f8c330]
|
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8182)[0x7ff4f6c23182]
|
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7ff4f613fb2d]
|