Форум

Вот выложил последние логи:

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 0x20000
/usr/libexec/mysqld(my_print_stacktrace+0x2e)[0x78ee3e]
/usr/libexec/mysqld(handle_fatal_signal+0x493)[0x6771f3]
/lib64/libpthread.so.0(+0xf7e0)[0x7f91a11d57e0]
/lib64/libc.so.6(gsignal+0x35)[0x7f919f61a5e5]
/lib64/libc.so.6(abort+0x175)[0x7f919f61bdc5]
/usr/libexec/mysqld[0x8256d4]
/usr/libexec/mysqld[0x825b47]
/usr/libexec/mysqld[0x8e38ff]
/usr/libexec/mysqld[0x8d9c85]
/usr/libexec/mysqld[0x824395]
/usr/libexec/mysqld[0x8175dc]
/usr/libexec/mysqld[0x81b713]
/lib64/libpthread.so.0(+0x7aa1)[0x7f91a11cdaa1]
/lib64/libc.so.6(clone+0x6d)[0x7f919f6d0aad]
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.
170605 16:14:31 mysqld_safe Number of processes running now: 0
170605 16:14:31 mysqld_safe mysqld restarted
170605 16:14:31 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
170605 16:14:31 [Note] /usr/libexec/mysqld (mysqld 5.5.50) starting as process 20708 ...
170605 16:14:31 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
170605 16:14:31 [Note] Plugin 'FEDERATED' is disabled.
170605 16:14:31 InnoDB: The InnoDB memory heap is disabled
170605 16:14:31 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170605 16:14:31 InnoDB: Compressed tables use zlib 1.2.3
170605 16:14:31 InnoDB: Using Linux native AIO
170605 16:14:31 InnoDB: Initializing buffer pool, size = 512.0M
170605 16:14:31 InnoDB: Completed initialization of buffer pool
170605 16:14:31 InnoDB: highest supported file format is Barracuda.