Помогите с mysql-server не запускается((

[ggg-]

Не запускается mysql. Не знаю что делать(((

Выкладываю логи:

(Нажмите, чтобы показать/скрыть)

160530 13:24:26 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
160530 13:24:26 [Note] /usr/sbin/mysqld (mysqld 5.5.43-MariaDB-1~precise-log) starting as process 4042 ...
160530 13:24:26 InnoDB: The InnoDB memory heap is disabled
160530 13:24:26 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160530 13:24:26 InnoDB: Compressed tables use zlib 1.2.3.4
160530 13:24:26 InnoDB: Using Linux native AIO
160530 13:24:26 InnoDB: Initializing buffer pool, size = 2.0G
160530 13:24:27 InnoDB: Completed initialization of buffer pool
160530 13:24:27 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 16100349735
160530 13:24:27  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 16100354898
160530 13:24:28  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 160530 13:24:28 [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 http://kb.askmonty.org/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: 5.5.43-MariaDB-1~precise-log
key_buffer_size=16777216
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 = 352025 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x0
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+0x2b)[0xa79d9b]
/usr/sbin/mysqld(handle_fatal_signal+0x398)[0x6cfc58]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x7f2cd007fcb0]
/usr/sbin/mysqld[0x92d396]
/usr/sbin/mysqld[0x92e814]
/usr/sbin/mysqld[0x9152dc]
/usr/sbin/mysqld[0x916faa]
160530 13:24:26 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
160530 13:24:26 [Note] /usr/sbin/mysqld (mysqld 5.5.43-MariaDB-1~precise-log) starting as process 4042 ...
160530 13:24:26 InnoDB: The InnoDB memory heap is disabled
160530 13:24:26 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160530 13:24:26 InnoDB: Compressed tables use zlib 1.2.3.4
160530 13:24:26 InnoDB: Using Linux native AIO
160530 13:24:26 InnoDB: Initializing buffer pool, size = 2.0G
160530 13:24:27 InnoDB: Completed initialization of buffer pool
160530 13:24:27 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 16100349735
160530 13:24:27  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 16100354898
160530 13:24:28  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 160530 13:24:28 [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 http://kb.askmonty.org/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: 5.5.43-MariaDB-1~precise-log
key_buffer_size=16777216
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 = 352025 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x0
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+0x2b)[0xa79d9b]
/usr/sbin/mysqld(handle_fatal_signal+0x398)[0x6cfc58]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x7f2cd007fcb0]
/usr/sbin/mysqld[0x92d396]
/usr/sbin/mysqld[0x92e814]
/usr/sbin/mysqld[0x9152dc]
/usr/sbin/mysqld[0x916faa]
/usr/sbin/mysqld[0x89bb87]
/usr/sbin/mysqld[0x8db666]
/usr/sbin/mysqld[0x848848]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x7f2cd0077e9a]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f2cce70b38d]
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.
160530 13:24:28 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended


mysqld_safe --log-error=/var/log/mysql.err

160530 13:27:44 mysqld_safe Can't log to error log and syslog at the same time.  Remove all --log-error configuration options for --syslog to take effect.
160530 13:27:44 mysqld_safe Logging to '/var/log/mysql.err'.
160530 13:27:44 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
160530 13:27:46 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

Помоги с данной задачей(. Спасибо.

1.4. Листинги и содержимое текстовых файлов следует добавлять в сообщение с помощью тегов [spoiler]...[/spoiler] или [code]...[/code], либо прикреплять к сообщению в виде отдельного файла.

--toZen
ТС не появлялся на Форуме более полугода по состоянию на 14/07/2019 (последняя явка: 03/06/2016). Модератором раздела принято решение закрыть тему.
--zg_nico

[spk-ubuntu]

[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.

Переустанавливать пробовали?

[ggg-]

Пробовал, но проблема остается та же. Минус в том что дамп базы не сделал. Помогите с проблемой. Очень нужно.