数据库crash已解决悬赏5积分

# cat /opt/zbox/logs/mysql_error.log
2020-04-14 16:16:43 140341597616256 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2020-04-14 16:16:43 140341597616256 [Note] InnoDB: The InnoDB memory heap is disabled
2020-04-14 16:16:43 140341597616256 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-04-14 16:16:43 140341597616256 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2020-04-14 16:16:43 140341597616256 [Note] InnoDB: Compressed tables use zlib 1.2.7
2020-04-14 16:16:43 140341597616256 [Note] InnoDB: Using generic crc32 instructions
2020-04-14 16:16:43 140341597616256 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2020-04-14 16:16:43 140341597616256 [Note] InnoDB: Completed initialization of buffer pool
2020-04-14 16:16:44 140341597616256 [Note] InnoDB: Highest supported file format is Barracuda.
2020-04-14 16:16:44 140341597616256 [Note] InnoDB: Starting crash recovery from checkpoint LSN=1600809
2020-04-14 16:16:44 140341597616256 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
2020-04-14 16:16:44 140341597616256 [Note] InnoDB: 128 rollback segment(s) are active.
2020-04-14 16:16:44 140341597616256 [Note] InnoDB: Waiting for purge to start
2020-04-14 16:16:44 140341597616256 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.35-80.0 started; log sequence number 1600819
200414 16:16:44 [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 https://mariadb.com/kb/en/reporting-bugs

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: 10.1.22-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=153
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 137009 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 = 0x0 thread_stack 0x30000
/opt/zbox/run/mysql/mysqld(my_print_stacktrace+0x29)[0x56241e9078d9]
/opt/zbox/run/mysql/mysqld(handle_fatal_signal+0x305)[0x56241e4c73d5]
/opt/zbox/run/lib/libpthread.so.0(+0xf6d0)[0x7fa3d2d086d0]
/opt/zbox/run/lib/ld-linux-x86-64.so.2(+0xbd56)[0x7fa3d2f23d56]
/opt/zbox/run/lib/ld-linux-x86-64.so.2(+0x147ac)[0x7fa3d2f2c7ac]
/opt/zbox/run/lib/ld-linux-x86-64.so.2(+0xf914)[0x7fa3d2f27914]
/opt/zbox/run/lib/ld-linux-x86-64.so.2(+0x13ccb)[0x7fa3d2f2bccb]
/opt/zbox/run/lib/libc.so.6(+0x13d082)[0x7fa3d109e082]
/opt/zbox/run/lib/ld-linux-x86-64.so.2(+0xf914)[0x7fa3d2f27914]
/opt/zbox/run/lib/libc.so.6(__libc_dlopen_mode+0x52)[0x7fa3d109e142]
/opt/zbox/run/lib/libpthread.so.0(+0xfe53)[0x7fa3d2d08e53]
/opt/zbox/run/lib/libpthread.so.0(+0x1001c)[0x7fa3d2d0901c]
/opt/zbox/run/lib/libpthread.so.0(__pthread_unwind+0x42)[0x7fa3d2d07332]
/opt/zbox/run/lib/libpthread.so.0(+0x8e77)[0x7fa3d2d01e77]
/opt/zbox/run/mysql/mysqld(+0x7476e4)[0x56241e6866e4]
/opt/zbox/run/mysql/mysqld(+0x731b33)[0x56241e670b33]
/opt/zbox/run/lib/libpthread.so.0(+0x7e25)[0x7fa3d2d00e25]
/opt/zbox/run/lib/libc.so.6(clone+0x6d)[0x7fa3d105fbad]
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.