Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.2.7
-
CentOS 7, Linux 3.10.0-514.26.2.el7.x86_64 #1 SMP Tue Jul 4 15:04:05 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Description
The MariaDB crashed with an assertion failure. At that time there was a large transaction running with (according to the rollback log) approx. 4191650 row operations.
2017-08-15 15:33:20 0x7fc018037700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.2.7/storage/innobase/dict/dict0stats.cc line 1572
|
InnoDB: Failing assertion: offsets_rec != 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.7/en/forcing-innodb-recovery.html
|
InnoDB: about forcing recovery.
|
170815 15:33:20 [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.2.7-MariaDB
|
key_buffer_size=16777216
|
read_buffer_size=2097152
|
max_used_connections=101
|
max_threads=102
|
thread_count=26
|
It is possible that mysqld could use up to
|
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 436307 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 0x49000
|
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x7fc13e53d37e]
|
/usr/sbin/mysqld(handle_fatal_signal+0x30d)[0x7fc13df82fad]
|
/lib64/libpthread.so.0(+0xf370)[0x7fc13d4f0370]
|
/lib64/libc.so.6(gsignal+0x37)[0x7fc13ba791d7]
|
/lib64/libc.so.6(abort+0x148)[0x7fc13ba7a8c8]
|
/usr/sbin/mysqld(+0x422d82)[0x7fc13dd42d82]
|
/usr/sbin/mysqld(+0xa727c0)[0x7fc13e3927c0]
|
/usr/sbin/mysqld(+0xa749c7)[0x7fc13e3949c7]
|
/usr/sbin/mysqld(+0xa781ed)[0x7fc13e3981ed]
|
/usr/sbin/mysqld(+0xa7a283)[0x7fc13e39a283]
|
/lib64/libpthread.so.0(+0x7dc5)[0x7fc13d4e8dc5]
|
/lib64/libc.so.6(clone+0x6d)[0x7fc13bb3b76d]
|
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.
|
Attachments
Issue Links
- causes
-
-
- Closed
-
- is caused by
-
-
- Closed
-
- is duplicated by
-
-
- Closed
-