問(wèn)題描述

系統(tǒng)是 centos6.5 安裝的 AMH4.2 ，昨天下午網(wǎng)站始終打不開(kāi)，于是我想重啟 MySQL ，用 amh 自帶的命令： amh mysql 然后選擇 restart ，但是，那個(gè) MySQL 一直關(guān)不了，等了好久都關(guān)不了，我一時(shí)心急，做出了一個(gè)錯(cuò)誤的決定，關(guān)機(jī)重啟，重啟之后， amh 的 nginx 和 php 能正常啟動(dòng)，就是 MySQL 一直啟動(dòng)不了，我用 amh mysql 命令，選擇了 start ，始終顯示這個(gè)錯(cuò)誤信息：

[AMH] MySQL Management please select: (1~6) 1) start 3) restart 5) force-reload 2) stop 4) reload 6) exit

Starting MySQL.The server quit without updating PID file (/[FAILED]l/mysql/data/ns471333.eu.pid). 把網(wǎng)上的做法全部試完了都不行，比如這個(gè)帖子里面的： http://stackoverflow.com/ques... 比如刪除錯(cuò)誤的err文件，刪除my.cnf文件都試過(guò)了，始終啟動(dòng)不了

求 MySQL 高手解疑一下吧，謝謝，謝謝 ，真的快急死人了

這是error.log信息： 160810 00:15:00 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data 160810 0:15:00 [Note] Plugin ’InnoDB’ is disabled. 22:15:00 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.

key_buffer_size=16777216 read_buffer_size=262144 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 = 133467 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 0x30000 /usr/local/mysql/bin/mysqld(my_print_stacktrace+0x33)[0x838bdb3] /usr/local/mysql/bin/mysqld(handle_fatal_signal+0x432)[0x8280302] [0xa0af2400] /usr/local/mysql/bin/mysqld(wait_for_free_space+0x5c)[0x837368c] /usr/local/mysql/bin/mysqld(my_write+0x102)[0x838a602] /usr/local/mysql/bin/mysqld(my_b_flush_io_cache+0x43a)[0x8376dfa] /usr/local/mysql/bin/mysqld(_ZN13MYSQL_BIN_LOG21sync_purge_index_fileEv+0x20)[0x82fcc10] /usr/local/mysql/bin/mysqld(_ZN13MYSQL_BIN_LOG4openEPKc13enum_log_typeS1_10cache_typebmbb+0xc9)[0x83027a9] /usr/local/mysql/bin/mysqld[0x812a116] /usr/local/mysql/bin/mysqld(_Z11mysqld_mainiPPc+0x3a1)[0x812c9d1] /usr/local/mysql/bin/mysqld(main+0x1b)[0x8123edb] /lib/libc.so.6(__libc_start_main+0xe6)[0xa07c7d26] /usr/local/mysql/bin/mysqld[0x8123e21] The manual page at http://dev.mysql.com/doc/mysq... contains information that should help you find out what is causing the crash. 160810 00:15:00 mysqld_safe mysqld from pid file /usr/local/mysql/data/ns471333.eu.pid ended 160810 00:21:36 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data 160810 0:21:36 [Note] Plugin ’InnoDB’ is disabled. 22:21:36 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.

key_buffer_size=16777216 read_buffer_size=262144 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 = 133467 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 0x30000 /usr/local/mysql/bin/mysqld(my_print_stacktrace+0x33)[0x838bdb3] /usr/local/mysql/bin/mysqld(handle_fatal_signal+0x432)[0x8280302] [0xa52d9400] /usr/local/mysql/bin/mysqld(wait_for_free_space+0x5c)[0x837368c] /usr/local/mysql/bin/mysqld(my_write+0x102)[0x838a602] /usr/local/mysql/bin/mysqld(my_b_flush_io_cache+0x43a)[0x8376dfa] /usr/local/mysql/bin/mysqld(_ZN13MYSQL_BIN_LOG21sync_purge_index_fileEv+0x20)[0x82fcc10] /usr/local/mysql/bin/mysqld(_ZN13MYSQL_BIN_LOG4openEPKc13enum_log_typeS1_10cache_typebmbb+0xc9)[0x83027a9] /usr/local/mysql/bin/mysqld[0x812a116] /usr/local/mysql/bin/mysqld(_Z11mysqld_mainiPPc+0x3a1)[0x812c9d1] /usr/local/mysql/bin/mysqld(main+0x1b)[0x8123edb] /lib/libc.so.6(__libc_start_main+0xe6)[0xa4faed26] /usr/local/mysql/bin/mysqld[0x8123e21]

The manual page at http://dev.mysql.com/do160810 00:21:36 mysqld_safe mysqld from pid file /usr/local/mysql/data/ns471333.eu.pid ended

現(xiàn)在才感覺(jué)到MySQL是如此脆弱不堪一擊，如果要重裝MySQL，怎樣在AMH4.2中重裝MySQL？

問(wèn)題解答

回答1：

This could be because you hit a bug.程序已經(jīng)提示或許是bug導(dǎo)致的