Debian 上的 MySQL 崩溃

问题描述

我正在尝试启动 MysqL 服务器但没有启动,我在 miserver.err 中有此错误,没有找到此问题的解决方

210602 13:01:08 MysqLd_safe Starting MysqLd daemon with databases from /var/lib/MysqL
210602 13:01:08 [Note] /usr/sbin/MysqLd (MysqLd 5.5.50-0+deb7u2) starting as process 9843 ...
210602 13:01:08 [Note] Plugin 'FEDERATED' is disabled.
210602 13:01:08 InnoDB: The InnoDB memory heap is disabled
210602 13:01:08 InnoDB: Mutexes and rw_locks use GCC atomic builtins
210602 13:01:08 InnoDB: Compressed tables use zlib 1.2.7
210602 13:01:08 InnoDB: Using Linux native AIO
210602 13:01:08 InnoDB: Initializing buffer pool,size = 128.0M
210602 13:01:08 InnoDB: Completed initialization of buffer pool
210602 13:01:08 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 568381145017
210602 13:01:08  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 568381664247
210602 13:01:09  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 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 18:01:09 UTC - 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.
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.

96 key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
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 = 338509 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...
97 stack_bottom = 0 thread_stack 0x40000
98 99 /usr/sbin/MysqLd(my_print_stacktrace+0x29)[0x7f51f3e1c869]
/usr/sbin/MysqLd(handle_fatal_signal+0x3d8)[0x7f51f3d032b8]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x11100)[0x7f51f34ad100]
/usr/sbin/MysqLd(+0x630535)[0x7f51f3f0e535]
/usr/sbin/MysqLd(+0x631857)[0x7f51f3f0f857]
/usr/sbin/MysqLd(+0x61eda0)[0x7f51f3efcda0]
/usr/sbin/MysqLd(+0x6206a2)[0x7f51f3efe6a2]
/usr/sbin/MysqLd(+0x5c1a83)[0x7f51f3e9fa83]
/usr/sbin/MysqLd(+0x5eed39)[0x7f51f3eccd39]
/usr/sbin/MysqLd(+0x57e6d8)[0x7f51f3e5c6d8]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7464)[0x7f51f34a3464]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x5f)[0x7f51f1d5ca0f]
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.
210602 13:01:09 MysqLd_safe MysqLd from pid file /var/lib/MysqL/protcloud.com.pid ended

我正在尝试启动 MysqL 并且不起作用,我也尝试过

MysqLd_safe --skip-grant-tables &

而且不工作 求助!我的操作系统是 Debian Wheezy 8 我的服务器在 PowerEdge R240 Dell 上运行

解决方法

暂无找到可以解决该程序问题的有效方法,小编努力寻找整理中!

如果你已经找到好的解决方法,欢迎将解决方案带上本链接一起发送给小编。

小编邮箱:dio#foxmail.com (将#修改为@)