Упал Mysql И не подымается.

[RoDGeR]

Сегодня ночью упал mysql и не подымается, какие либо извинения на сервере не проводились.

service mysql start

SpoilerShow

Code: Select all

root@s11:~# service mysql start
[FAIL] Starting MySQL database server: mysqld . . . . . . . . . . . . . . failed!
root@s11:~#

/var/log/mysql/error.log

SpoilerShow

Code: Select all

150921 14:43:55 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
150921 14:43:55 [Note] /usr/sbin/mysqld (mysqld 5.5.44-0+deb7u1) starting as process 16149 ...
150921 14:43:55 [Note] Plugin 'FEDERATED' is disabled.
150921 14:43:55 InnoDB: The InnoDB memory heap is disabled
150921 14:43:55 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150921 14:43:55 InnoDB: Compressed tables use zlib 1.2.7
150921 14:43:55 InnoDB: Using Linux native AIO
150921 14:43:55 InnoDB: Initializing buffer pool, size = 128.0M
150921 14:43:55 InnoDB: Completed initialization of buffer pool
150921 14:43:55 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
150921 14:43:55  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: Error: tried to read 16384 bytes at offset 0 5259264.
InnoDB: Was only able to read 12288.
InnoDB: Fatal error: cannot read from file. OS error number 17.
150921 14:44:19  InnoDB: Assertion failure in thread 140320680806176 in file os0file.c line 2538
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
11:44:19 UTC - 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.
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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=200
thread_count=0
connection_count=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 445698 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 = 0 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x29)[0x7f9ef4aacd89]
/usr/sbin/mysqld(handle_fatal_signal+0x3d8)[0x7f9ef4993ed8]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf0a0)[0x7f9ef41410a0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35)[0x7f9ef29d3165]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x180)[0x7f9ef29d63e0]
/usr/sbin/mysqld(+0x62e42b)[0x7f9ef4b9e42b]
/usr/sbin/mysqld(+0x5f3e90)[0x7f9ef4b63e90]
/usr/sbin/mysqld(+0x5cfc19)[0x7f9ef4b3fc19]
/usr/sbin/mysqld(+0x5d05bc)[0x7f9ef4b405bc]
/usr/sbin/mysqld(+0x5c1098)[0x7f9ef4b31098]
/usr/sbin/mysqld(+0x5ad58f)[0x7f9ef4b1d58f]
/usr/sbin/mysqld(+0x5b77d7)[0x7f9ef4b277d7]
/usr/sbin/mysqld(+0x5e42b9)[0x7f9ef4b542b9]
/usr/sbin/mysqld(+0x5d69f3)[0x7f9ef4b469f3]
/usr/sbin/mysqld(+0x583a37)[0x7f9ef4af3a37]
/usr/sbin/mysqld(+0x54fb6f)[0x7f9ef4abfb6f]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x41)[0x7f9ef4996261]
/usr/sbin/mysqld(+0x333047)[0x7f9ef48a3047]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0xa73)[0x7f9ef48a60c3]
/usr/sbin/mysqld(+0x2b9185)[0x7f9ef4829185]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x45b)[0x7f9ef4829dfb]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd)[0x7f9ef29bfead]
/usr/sbin/mysqld(+0x2b0f79)[0x7f9ef4820f79]
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.
150921 14:44:19 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

/etc/mysql/my.cnf

SpoilerShow

Code: Select all

[client]
port=3306
socket=/var/run/mysqld/mysqld.sock

[mysqld_safe]
socket=/var/run/mysqld/mysqld.sock

[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
log_error=/var/log/mysql/error.log
max_connections=200
max_user_connections=30
wait_timeout=30
interactive_timeout=50
long_query_time=5
innodb_file_per_table

!includedir /etc/mysql/conf.d/

[Deeryo]

Проверь, живы ли жесткие диски.
Можно попробовать восстановить базу, перед этим лучше забэкапить всю папку mysql.
http://forum.vestacp.com/viewtopic.php? ... 383#p29136

[RoDGeR]

Code: Select all

Ну то есть так:
1) Добавляем в /etc/my.cnf строку innodb_force_recovery=2 в разделе [mysqld].
2) Запускаем сервис mysql
3) Бэкапим все базы данных командой mysqldump:
mysqldump -A > fullbackup.sql
*Если все базы успешно задампились, то продолжаем восстанавливать из sql файлa, иначе придется дампить по одной базе в отдельные файлы. Какие-то из них потеряем...
4) Останавливаем mysql
5) Переносим из папки /var/lib/mysql файлы ibdata*, ib_logfile* и все папки, кроме mysql, в укромное место. В папке /var/lib/mysql останется только подпапка mysql.
6) Убираем innodb_force_recovery=2 из /etc/my.cnf
7) Запускаем mysql
8) Восстанавливаем все базы данных из sql дампа:
mysql < fullbackup.sql

1) Добавляем в /etc/my.cnf строку innodb_force_recovery=2 в разделе [mysqld].
2) Запускаем сервис mysql

после первого пункта сервис все равно не запускается.

[Deeryo]

Пробуй innodb_force_recovery=6 (это описано тут https://dev.mysql.com/doc/refman/5.0/en ... overy.html)

[RoDGeR]

К сожалению не помогло (

[Deeryo]

Может файл какой-то не читается. В логе было InnoDB: Fatal error: cannot read from file. OS error number 17.
Попробуй сделать архив всей папки mysql.

[skurudo]

Возможно стоит более жестко подойти к вопросу и сделать fsck