MySQL Forums
Forum List  »  Russian

Проблема с MySQL на сервере zabbix 2.4.5
Posted by: Amir Amir
Date: July 18, 2016 02:30AM

Добрый день! Из-за скачка напряжения сервак, на котором работал MySQL, был жестко обесточен. При восстановлении электропитания возникла проблема с MySQL. При старте он сразу вылетает, причем в логи ничего не пишет. Запуск через mysqld_safe показал в логах следующее:

160718 10:38:00 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
160718 10:38:00 [Note] /usr/sbin/mysqld (mysqld 5.5.46-MariaDB-log) starting as process 2969 ...
160718 10:38:00 InnoDB: The InnoDB memory heap is disabled
160718 10:38:00 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160718 10:38:00 InnoDB: Compressed tables use zlib 1.2.8
160718 10:38:00 InnoDB: Using Linux native AIO
160718 10:38:00 InnoDB: Initializing buffer pool, size = 128.0M
160718 10:38:00 InnoDB: Completed initialization of buffer pool
160718 10:38:00 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 2414755548105
160718 10:38:00 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 2414760790528
InnoDB: Doing recovery: scanned up to log sequence number 2414761460674
InnoDB: 2 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 107 row operations to undo
InnoDB: Trx id counter is 474FFE00
160718 10:38:01 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 160718 10:38:01 [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

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.46-MariaDB-log
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 466702 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 0x48000
The manual page at contains
information that should help you find out what is causing the crash.
160718 10:38:01 mysqld_safe mysqld from pid file /var/lib/mysql/ ended
В общем, некая ошибка [ERROR] mysqld got signal 11 ; приводит к тому, что MySQL не запускается ни в какую. Гугл не помог. С MySQL, к сожалению, я толком не работал и копать глубже самостоятельно уже не смогу.
Очень рассчитываю что данный форум поможет мне. Заранее спасибо!

Options: ReplyQuote

Written By
Проблема с MySQL на сервере zabbix 2.4.5
July 18, 2016 02:30AM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.