[MDEV-20995] Server crashes on innodb assertion error Created: 2019-11-06  Updated: 2019-11-06  Resolved: 2019-11-06

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB, Storage Engine - XtraDB
Affects Version/s: 10.1.42
Fix Version/s: 10.2.29, 10.1.43, 10.3.20, 10.4.10

Type: Bug Priority: Major
Reporter: Jiri Lunacek Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Environment:

CentOS 7


Issue Links:
Duplicate
duplicates MDEV-20987 InnoDB fails to start when fts table ... Closed

 Description   

After update to version 10.1.42 server will not start complaining about assertion error. Downgrade to version 10.1.41 fixes the issue.

This happens even when databases are restored from dumps to a clean install.

mysql_error.log

2019-11-06 09:01:28 7f23bd794900  InnoDB: Assertion failure in thread 139791479425280 in file dict0dict.cc line 1493
InnoDB: Failing assertion: table->can_be_evicted
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: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
191106  9:01:28 [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.42-MariaDB
key_buffer_size=1073741824
read_buffer_size=524288
max_used_connections=0
max_threads=1002
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 17999162 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 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x56483cb05a5e]
/usr/sbin/mysqld(handle_fatal_signal+0x305)[0x56483c628455]
sigaction.c:0(__restore_rt)[0x7f23bd3815f0]
:0(__GI_raise)[0x7f23bb41e337]
:0(__GI_abort)[0x7f23bb41fa28]
/usr/sbin/mysqld(+0x9e3db0)[0x56483ca44db0]
/usr/sbin/mysqld(+0x9f656b)[0x56483ca5756b]
/usr/sbin/mysqld(+0x9f6f87)[0x56483ca57f87]
/usr/sbin/mysqld(+0x9e35e0)[0x56483ca445e0]
/usr/sbin/mysqld(+0xa37078)[0x56483ca98078]
/usr/sbin/mysqld(+0xa43182)[0x56483caa4182]
/usr/sbin/mysqld(+0x8b7f83)[0x56483c918f83]
/usr/sbin/mysqld(+0x949ee9)[0x56483c9aaee9]
/usr/sbin/mysqld(+0x866785)[0x56483c8c7785]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x64)[0x56483c62a7c4]
/usr/sbin/mysqld(+0x44b630)[0x56483c4ac630]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0xa1a)[0x56483c4adf2a]
/usr/sbin/mysqld(+0x3a1ba1)[0x56483c402ba1]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x550)[0x56483c406a80]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7f23bb40a505]
/usr/sbin/mysqld(+0x3990dd)[0x56483c3fa0dd]
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



 Comments   
Comment by Marko Mäkelä [ 2019-11-06 ]

This issue has already been reported and addressed in MDEV-20987.

Generated at Thu Feb 08 09:03:48 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.