Answer the question
In order to leave comments, you need to log in
Why does mysqldump crash MySQL?
Database 10.1.23-MariaDB
When dumping an InnoDB table with ~4,278,134 records and a size of 23.3Gb, the database with this log crashes
terminate called after throwing an instance of 'std::out_of_range'
what(): vector::_M_range_check
170513 23:48:21 [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.23-MariaDB
key_buffer_size=536870912
read_buffer_size=131072
max_used_connections=8
max_threads=153
thread_count=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 860337 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/sbin/mysqld(my_print_stacktrace+0x2e)[0x7f20a3cba4ce]
/usr/sbin/mysqld(handle_fatal_signal+0x305)[0x7f20a37dd345]
/lib64/libpthread.so.0(+0xf370)[0x7f20a2df7370]
/lib64/libc.so.6(gsignal+0x37)[0x7f20a114c1d7]
/lib64/libc.so.6(abort+0x148)[0x7f20a114d8c8]
/lib64/libstdc++.so.6(_ZN9__gnu_cxx27__verbose_terminate_handlerEv+0x165)[0x7f20a183a9d5]
/lib64/libstdc++.so.6(+0x5e946)[0x7f20a1838946]
/lib64/libstdc++.so.6(+0x5e973)[0x7f20a1838973]
/lib64/libstdc++.so.6(+0x5eb93)[0x7f20a1838b93]
/lib64/libstdc++.so.6(_ZSt20__throw_out_of_rangePKc+0x77)[0x7f20a188da17]
/usr/sbin/mysqld(+0x8d97a0)[0x7f20a3aff7a0]
/usr/sbin/mysqld(+0x8de3a3)[0x7f20a3b043a3]
/usr/sbin/mysqld(+0x8e0805)[0x7f20a3b06805]
/usr/sbin/mysqld(+0x8e2573)[0x7f20a3b08573]
/lib64/libpthread.so.0(+0x7dc5)[0x7f20a2defdc5]
/lib64/libc.so.6(clone+0x6d)[0x7f20a120e73d]
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.
[mysqld]
innodb_file_per_table = 1
innodb_large_prefix = 1
innodb_file_format = Barracuda
max_allowed_packet = 600MB
tmp_table_size = 32MB
max_heap_table_size = 32MB
innodb_buffer_pool_size = 512MB
key_buffer_size = 512MB
query_cache_size = 4MB
query_cache_limit = 2MB
table_open_cache = 20000
thread_cache_size = 20
net_read_timeout = 900
net_write_timeout = 600
Answer the question
In order to leave comments, you need to log in
There is nothing specific in the error for non-developers.
Write to the database bug tracker.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question