Resolved Mysql crash - Innodb corrupt ???

[GoneD]

Hi here,

I have a problem on my Plesk 12.5 :

Mysql is crash and doesn't want to start :

See log:


##
2017-06-02 20:07:06 5039 [Note] Plugin 'FEDERATED' is disabled.
2017-06-02 20:07:06 5039 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-06-02 20:07:06 5039 [Note] InnoDB: The InnoDB memory heap is disabled
2017-06-02 20:07:06 5039 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-06-02 20:07:06 5039 [Note] InnoDB: Memory barrier is not used
2017-06-02 20:07:06 5039 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-06-02 20:07:06 5039 [Note] InnoDB: Using Linux native AIO
2017-06-02 20:07:06 5039 [Note] InnoDB: Using CPU crc32 instructions
2017-06-02 20:07:06 5039 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-06-02 20:07:06 5039 [Note] InnoDB: Completed initialization of buffer pool
2017-06-02 20:07:06 5039 [Note] InnoDB: Highest supported file format is Barracuda.
2017-06-02 20:07:06 5039 [Note] InnoDB: Log scan progressed past the checkpoint lsn 19977419245
2017-06-02 20:07:06 5039 [Note] InnoDB: Database was not shutdown normally!
2017-06-02 20:07:06 5039 [Note] InnoDB: Starting crash recovery.
2017-06-02 20:07:06 5039 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-06-02 20:07:06 5039 [Note] InnoDB: Restoring possible half-written data pages
2017-06-02 20:07:06 5039 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 19977537893
2017-06-02 20:07:06 5039 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 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 18:07:06 UTC - mysqld got signal 11 ;
52 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
53 read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
54 connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68108 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
55 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...
56 57 58 59 60 stack_bottom = 0 thread_stack 0x40000
61 62 63 64 65 66 67 68 69 70 71 72 73 74 /usr/sbin/mysqld(my_print_stacktrace+0x35)[0x8e5d85]
75 76 77 78 79 80 81 /usr/sbin/mysqld(handle_fatal_signal+0x494)[0x6692b4]
82 /lib64/libpthread.so.0(+0xf7e0)[0x7fe8996477e0]
83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 /usr/sbin/mysqld[0x9953fd]
98 99 /usr/sbin/mysqld[0x99710f]
/usr/sbin/mysqld[0x97f7ce]
/usr/sbin/mysqld[0x9814b4]
/usr/sbin/mysqld[0xa4f69f]
/usr/sbin/mysqld[0xa92470]
/usr/sbin/mysqld[0x9fb128]
/lib64/libpthread.so.0(+0x7aa1)[0x7fe89963faa1]
/lib64/libc.so.6(clone+0x6d)[0x7fe898180bcd]
The manual page at MySQL :: MySQL 5.7 Reference Manual :: B.5.3.3 What to Do If MySQL Keeps Crashing contains
information that should help you find out what is causing the crash.
##

Thanks for help

Regards,

 

[GoneD]

Well done resolve myself,

Thanks for help