av一区二区在线观看_亚洲男人的天堂网站_日韩亚洲视频_在线成人免费_欧美日韩精品免费观看视频_久草视

您的位置:首頁技術文章
文章詳情頁

MySQL 啟動不了,始終顯示“The server quit without updating PID file”

瀏覽:122日期:2022-06-19 15:30:37

問題描述

系統是 centos6.5 安裝的 AMH4.2 ,昨天下午網站始終打不開,于是我想重啟 MySQL ,用 amh 自帶的命令: amh mysql 然后選擇 restart ,但是,那個 MySQL 一直關不了,等了好久都關不了,我一時心急,做出了一個錯誤的決定,關機重啟,重啟之后, amh 的 nginx 和 php 能正常啟動,就是 MySQL 一直啟動不了,我用 amh mysql 命令,選擇了 start ,始終顯示這個錯誤信息:

[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). 把網上的做法全部試完了都不行,比如這個帖子里面的: http://stackoverflow.com/ques... 比如刪除錯誤的err文件,刪除my.cnf文件都試過了,始終啟動不了

求 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

現在才感覺到MySQL是如此脆弱不堪一擊,如果要重裝MySQL,怎樣在AMH4.2中重裝MySQL?

問題解答

回答1:

This could be because you hit a bug.程序已經提示或許是bug導致的

相關文章:
主站蜘蛛池模板: 妞干网视频 | a级黄色片在线观看 | 亚洲精品1区 | 欧美一区二区免费 | 亚洲欧美日本在线 | 欧美a级网站 | 在线一区| 亚洲精品久久久蜜桃 | 国产人成精品一区二区三 | 日本免费一区二区三区 | 激情毛片 | 91免费看片神器 | 日韩中文字幕在线免费 | 精品亚洲一区二区 | 亚洲精品久久久久久久久久久 | 亚洲视频在线看 | 天天综合网天天综合 | 九九热这里只有精品在线观看 | 午夜免费视频观看 | 99免费看| 亚洲免费影院 | 色爽女 | 中文字幕免费中文 | 中文字字幕一区二区三区四区五区 | 香蕉二区| 可以免费看的毛片 | 亚洲一区二区视频在线观看 | 国产高清精品在线 | 精品视频导航 | 欧美激情区 | 99视频免费看 | 国产精品精品久久久 | 99热播精品| 欧美日韩专区 | 日韩三级视频 | 国产一区不卡在线观看 | 黄色免费av| 日韩精品一区二区久久 | 成人一区二区在线 | 夜夜夜夜夜夜曰天天天 | 国产在线精品一区二区 |