Страница 1 из 1

Во время дампа крушится база

UNREAD_POSTДобавлено: 13.05.2017 20:02:49
Во время дампа крушится база

База InnoDB ~22G

Sypex Dumper 2.0.11
Server version: 10.1.23-MariaDB

Config MariaDB

Код: Выделить всё
innodb_file_per_table    = 1
innodb_large_prefix    = 1
innodb_file_format       = Barracuda

max_allowed_packet       = 64000MB
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

Log dumper

Код: Выделить всё
 Warning: Empty row packet body (/src/simpltst/dumper/index.php:1078)

Log MariaDB

Код: Выделить всё
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
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
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.