Mysql перестал стартовал после перезагрузки. Бэкап есть, но в качестве дампа базы.
таблицы большие до 1-2 млн записей, innoDB.
161208 17:19:39 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
161208 17:19:39 [Note] /usr/sbin/mysqld (mysqld 5.5.46-0ubuntu0.14.04.2) starting as process 13140 ...
161208 17:19:39 [Note] Plugin 'FEDERATED' is disabled.
161208 17:19:39 InnoDB: The InnoDB memory heap is disabled
161208 17:19:39 InnoDB: Mutexes and rw_locks use GCC atomic builtins
161208 17:19:39 InnoDB: Compressed tables use zlib 1.2.8
161208 17:19:39 InnoDB: Using Linux native AIO
161208 17:19:39 InnoDB: Initializing buffer pool, size = 128.0M
161208 17:19:39 InnoDB: Completed initialization of buffer pool
161208 17:19:39 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 19401977706025
161208 17:19:39 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 19401977830069
161208 17:19:39 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 2 3 4 5 6 7 8 9 10 11 12 13 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 161208 17:19:39 InnoDB: Assertion failure in thread 140506955769600 in file trx0undo.c line 561
InnoDB: Failing assertion: free + TRX_UNDO_LOG_XA_HDR_SIZE < UNIV_PAGE_SIZE – 100
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to
.
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:
InnoDB: about forcing recovery.
14:19:39 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=1048576
max_used_connections=0
max_threads=50
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 = 162368 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+0x20)[0x7fca66567ec0]
/usr/sbin/mysqld(handle_fatal_signal+0x3d5)[0x7fca66452025]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10340)[0x7fca651e1340]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x39)[0x7fca64838cc9]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7fca6483c0d8]
/usr/sbin/mysqld(+0x55bb5d)[0x7fca665d1b5d]
/usr/sbin/mysqld(+0x55cc65)[0x7fca665d2c65]
/usr/sbin/mysqld(+0x5e0a0e)[0x7fca66656a0e]
/usr/sbin/mysqld(+0x5e213d)[0x7fca6665813d]
/usr/sbin/mysqld(+0x584687)[0x7fca665fa687]
/usr/sbin/mysqld(+0x5b1429)[0x7fca66627429]
/usr/sbin/mysqld(+0x541ed8)[0x7fca665b7ed8]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8182)[0x7fca651d9182]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fca648fc47d]
The manual page at
contains
information that should help you find out what is causing the crash.
161208 17:19:39 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended