SQLinfo.ru - Все о MySQL

Форум пользователей MySQL

Задавайте вопросы, мы ответим

Вы не зашли.

#1 05.02.2019 11:06:10

sintez
Участник
Зарегистрирован: 05.02.2019
Сообщений: 1

Падение MariaDB

Добрый день. Не являюсь специалистом в области баз данных. Постоянно сваливается mariadb вот с такими ошибками:

2019-02-05 10:57:35 139915286862080 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2019-02-05 10:57:35 139915286862080 [Note] InnoDB: The InnoDB memory heap is disabled
2019-02-05 10:57:35 139915286862080 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-02-05 10:57:35 139915286862080 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-02-05 10:57:35 139915286862080 [Note] InnoDB: Compressed tables use zlib 1.2.8
2019-02-05 10:57:35 139915286862080 [Note] InnoDB: Using Linux native AIO
2019-02-05 10:57:35 139915286862080 [Note] InnoDB: Using SSE crc32 instructions
2019-02-05 10:57:35 139915286862080 [Note] InnoDB: Initializing buffer pool, size = 2.0G
2019-02-05 10:57:35 139915286862080 [Note] InnoDB: Completed initialization of buffer pool
2019-02-05 10:57:35 139915286862080 [Note] InnoDB: Highest supported file format is Barracuda.
2019-02-05 10:57:35 139915286862080 [ERROR] InnoDB: Trying to access page number 4293139327 in space 0 space name ./ibdata1, which is outside the tablespace bounds. Byte offset 0, len 16384 i/o type 10.Please check that the configuration matches the InnoDB system tablespace location (ibdata files)
2019-02-05 10:57:35 7f4090f8d900  InnoDB: Assertion failure in thread 139915286862080 in file ha_innodb.cc line 22057
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/ … overy.html
InnoDB: about forcing recovery.
190205 10:57:35 [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=33554432
read_buffer_size=131072
max_used_connections=0
max_threads=153
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 368851 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 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55e26666039e]
/usr/sbin/mysqld(handle_fatal_signal+0x3bd)[0x55e2661a197d]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x110c0)[0x7f40909f60c0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcf)[0x7f408f563fff]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7f408f56542a]
/usr/sbin/mysqld(+0x830beb)[0x55e26642dbeb]
/usr/sbin/mysqld(+0x9d8633)[0x55e2665d5633]
/usr/sbin/mysqld(+0x9986dc)[0x55e2665956dc]
/usr/sbin/mysqld(+0x9998d9)[0x55e2665968d9]
/usr/sbin/mysqld(+0x979534)[0x55e266576534]
/usr/sbin/mysqld(+0x929b6e)[0x55e266526b6e]
/usr/sbin/mysqld(+0x92a5a5)[0x55e2665275a5]
/usr/sbin/mysqld(+0x92b7ce)[0x55e2665287ce]
/usr/sbin/mysqld(+0x913083)[0x55e266510083]
/usr/sbin/mysqld(+0x826821)[0x55e266423821]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x62)[0x55e2661a3ac2]
/usr/sbin/mysqld(+0x421285)[0x55e26601e285]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x7da)[0x55e26601f8ca]
/usr/sbin/mysqld(+0x379dac)[0x55e265f76dac]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x1b7e)[0x55e265f7a86e]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f408f5512e1]
/usr/sbin/mysqld(_start+0x2a)[0x55e265f6ea7a]
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.


Я так подозреваю, что дело в обычных настройках. Пожалуйста, подскажите в какую сторону смотреть?

Неактивен

 

#2 06.02.2019 12:19:27

paulus
Администратор
MySQL Authorized Developer and DBA
Зарегистрирован: 22.01.2007
Сообщений: 6712

Re: Падение MariaDB

Выглядит не как настройки, если честно.

Проверьте, что в конфиге innodb_data_file_path указывает в правильное место, и размеры реальные и в конфиге совпадают — это проверка гипотезы настроек.

Если совпадают, то дело в каких-то внутренних неправильных ссылках, и тогда правильно забэкапить все данные в текст (mysqldump -A | gzip > filename.sql.gz), остановить базу, удалить каталог с данными, пересоздать его (mysqld --initialize), запустить mysql, восстановить данные (gzcat filename.sql.gz | mysql).

Неактивен

 

Board footer

Работает на PunBB
© Copyright 2002–2008 Rickard Andersson