LINUX.ORG.RU
ФорумAdmin

Падает mariadb

 


0

1

Всем привет. Есть база, которую перенес с mysql на mariadb. Работает примерно сутки, крашится и больше не запускается.

Лог:

2019-02-05 14:27:05 140147802577152 [Note] InnoDB: 128 rollback segment(s) are active. 2019-02-05 14:27:05 140147802577152 [Note] InnoDB: Waiting for purge to start 2019-02-05 14:27:05 7f75807fb700 InnoDB: Assertion failure in thread 140142643754752 in file trx0purge.cc line 682 InnoDB: Failing assertion: purge_sys->iter.trx_no <= purge_sys->rseg->last_trx_no 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. 190205 14:27:05 [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.37-MariaDB-0+deb9u1 key_buffer_size=16777216 read_buffer_size=131072 max_used_connections=0 max_threads=162 thread_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 372238 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)[0x55e2398f739e] /usr/sbin/mysqld(handle_fatal_signal+0x3bd)[0x55e23943897d] 2019-02-05 14:27:05 140147802577152 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.41-84.1 started; log sequence number 275082322538 /lib/x86_64-linux-gnu/libpthread.so.0(+0x110c0)[0x7f76b3a3a0c0] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcf)[0x7f76b25a7fff] /lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7f76b25a942a] /usr/sbin/mysqld(+0x91ca84)[0x55e2397b0a84] /usr/sbin/mysqld(+0x91cf04)[0x55e2397b0f04] /usr/sbin/mysqld(+0x91dbd9)[0x55e2397b1bd9] /usr/sbin/mysqld(+0x90db54)[0x55e2397a1b54] /lib/x86_64-linux-gnu/libpthread.so.0(+0x7494)[0x7f76b3a30494] /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7f76b265dacf] 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. 2019-02-05 14:27:11 140428104173824 [Note] InnoDB: Using mutexes to ref count buffer pool pages 2019-02-05 14:27:11 140428104173824 [Note] InnoDB: The InnoDB memory heap is disabled 2019-02-05 14:27:11 140428104173824 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2019-02-05 14:27:11 140428104173824 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier 2019-02-05 14:27:11 140428104173824 [Note] InnoDB: Compressed tables use zlib 1.2.8 2019-02-05 14:27:11 140428104173824 [Note] InnoDB: Using Linux native AIO 2019-02-05 14:27:11 140428104173824 [Note] InnoDB: Using SSE crc32 instructions 2019-02-05 14:27:11 140428104173824 [Note] InnoDB: Initializing buffer pool, size = 4.0G 2019-02-05 14:27:11 140428104173824 [Note] InnoDB: Completed initialization of buffer pool 2019-02-05 14:27:11 140428104173824 [Note] InnoDB: Highest supported file format is Barracuda. 2019-02-05 14:27:11 140428104173824 [Note] InnoDB: Starting crash recovery from checkpoint LSN=275082321932 2019-02-05 14:27:11 140428104173824 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... 2019-02-05 14:27:17 140428104173824 [Note] InnoDB: 128 rollback segment(s) are active. 2019-02-05 14:27:17 140428104173824 [Note] InnoDB: Waiting for purge to start 2019-02-05 14:27:17 140428104173824 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.41-84.1 started; log sequence number 275082322548 2019-02-05 14:27:17 7fb6c3bfb700 InnoDB: Assertion failure in thread 140422944896768 in file trx0purge.cc line 682 InnoDB: Failing assertion: purge_sys->iter.trx_no <= purge_sys->rseg->last_trx_no 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. 190205 14:27:17 [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.37-MariaDB-0+deb9u1 key_buffer_size=16777216 read_buffer_size=131072 max_used_connections=0 max_threads=162 thread_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 372238 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)[0x55ba10e9339e] /usr/sbin/mysqld(handle_fatal_signal+0x3bd)[0x55ba109d497d] /lib/x86_64-linux-gnu/libpthread.so.0(+0x110c0)[0x7fb7f6ea90c0] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcf)[0x7fb7f5a16fff] /lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7fb7f5a1842a] /usr/sbin/mysqld(+0x91ca84)[0x55ba10d4ca84] /usr/sbin/mysqld(+0x91cf04)[0x55ba10d4cf04] /usr/sbin/mysqld(+0x91dbd9)[0x55ba10d4dbd9] /usr/sbin/mysqld(+0x90db54)[0x55ba10d3db54] /lib/x86_64-linux-gnu/libpthread.so.0(+0x7494)[0x7fb7f6e9f494] /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7fb7f5accacf] 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. 2019-02-05 14:27:23 140546441177344 [Note] InnoDB: Using mutexes to ref count buffer pool pages 2019-02-05 14:27:23 140546441177344 [Note] InnoDB: The InnoDB memory heap is disabled 2019-02-05 14:27:23 140546441177344 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2019-02-05 14:27:23 140546441177344 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier 2019-02-05 14:27:23 140546441177344 [Note] InnoDB: Compressed tables use zlib 1.2.8 2019-02-05 14:27:23 140546441177344 [Note] InnoDB: Using Linux native AIO 2019-02-05 14:27:23 140546441177344 [Note] InnoDB: Using SSE crc32 instructions 2019-02-05 14:27:23 140546441177344 [Note] InnoDB: Initializing buffer pool, size = 4.0G 2019-02-05 14:27:23 140546441177344 [Note] InnoDB: Completed initialization of buffer pool 2019-02-05 14:27:23 140546441177344 [Note] InnoDB: Highest supported file format is Barracuda. 2019-02-05 14:27:23 140546441177344 [Note] InnoDB: Starting crash recovery from checkpoint LSN=275082321932 2019-02-05 14:27:23 140546441177344 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...

Настройки:

[server]

[mysqld]

user = mysql pid-file = /var/run/mysqld/mysqld.pid socket = /var/run/mysqld/mysqld.sock port = 3306 basedir = /usr datadir = /var/lib/mysql tmpdir = /tmp lc-messages-dir = /usr/share/mysql skip-external-locking log_error = /var/log/mysql/error.log bind-address = 127.0.0.1

max_allowed_packet = 16M key_buffer_size = 16M innodb_buffer_pool_size = 4096M innodb_file_per_table = 1 innodb_flush_method = O_DIRECT innodb_flush_log_at_trx_commit = 0

max_connections = 160

query_cache_size = 0

slow_query_log = /var/log/mysql/mysql-slow.log long_query_time = 1

expire_logs_days = 10 max_binlog_size = 100M

[embedded]

[mariadb]

[mariadb-10.1]

Подскажите, что может быть не так?

Вы не можете добавлять комментарии в эту тему. Тема перемещена в архив.