SQLinfo.ru - Все о MySQL

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

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

Вы не зашли.

#1 08.11.2018 14:41:16

Откуда: Санкт-Петербург
Зарегистрирован: 04.09.2008
Сообщений: 172

Перестал запускаться сервер mariadb 10.3

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

2018-11-08 11:34:45 0 [Note] Using unique option prefix 'myisam-recover' is error-prone and can break in the future. Please use the full name 'myisam-recover-options' instead.
2018-11-08 11:34:45 0 [Note] mysqld: Aria engine: starting recovery
recovered pages: 0% 10%181108 11:34:45 [ERROR] mysqld got signal 11 ;
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.3.10-MariaDB-1:10.3.10+maria~jessie-log
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 22020736 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
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.



Board footer

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