MySQL無法啟動(dòng)的解決辦法
MySQL無法啟動(dòng)的解決辦法
MySQL無法啟動(dòng)
在停止mysql之后,執(zhí)行了一些操作(如修改主機(jī)名),重新啟動(dòng) mysql,發(fā)現(xiàn)起不來。
[root@www ~]$ service mysql start Starting MySQL..^[[A.................................................................................................. ERROR! The server quit without updating PID file (/disk/mysql/www.pid). [root@www ~]$ service mysql stop ERROR! MySQL server PID file could not be found! [root@www ~]$ service mysql stop ERROR! MySQL server PID file could not be found! [root@www ~]$ service mysql start Starting MySQL.................. 還是老樣子,只好 Ctr+C 掉。 [root@www ~]$
實(shí)在是啟動(dòng)不了,看一下日志:/disk/mysql/www.err
120608 09:56:17 mysqld_safe Starting mysqld daemon with databases from /disk/mysql 120608 9:56:17 [Note] Plugin 'FEDERATED' is disabled. 120608 9:56:17 InnoDB: The InnoDB memory heap is disabled 120608 9:56:17 InnoDB: Mutexes and rw_locks use InnoDB's own implementation 120608 9:56:17 InnoDB: Compressed tables use zlib 1.2.3 120608 9:56:17 InnoDB: Using Linux native AIO 120608 9:56:17 InnoDB: Initializing buffer pool, size = 128.0M 120608 9:56:17 InnoDB: Completed initialization of buffer pool InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. 120608 9:56:17 InnoDB: Retrying to lock the first data file InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 ...
好像是原來的 mysqld 并沒有停下來。
強(qiáng)制終止 mysqld
[root@www ~]$ ps -ef|grep mysql root 4769 1 0 Jun06 ? 00:00:00 /bin/sh /usr/bin/mysqld_safe --datadir=/disk/mysql --pid-file=/disk/mysql/localhost.pid mysql 4874 4769 0 Jun06 ? 00:04:04 /usr/sbin/mysqld --basedir=/usr --datadir=/disk/mysql --plugin-dir=/usr/lib/mysql/plugin --user=mysql --log-error=/disk/mysql/localhost.err --pid-file=/disk/mysql/localhost.pid --socket=/disk/mysql/mysql.sock root 17947 1 0 09:56 pts/1 00:00:00 /bin/sh /usr/bin/mysqld_safe --datadir=/disk/mysql --pid-file=/disk/mysql/www.pid mysql 18052 17947 0 09:56 pts/1 00:00:00 /usr/sbin/mysqld --basedir=/usr --datadir=/disk/mysql --plugin-dir=/usr/lib/mysql/plugin --user=mysql --log-error=/disk/mysql/www.err --pid-file=/disk/mysql/www.pid --socket=/disk/mysql/mysql.sock root 18099 17514 0 09:56 pts/1 00:00:00 grep mysql [root@www ~]$ killall mysqld [root@www ~]$ killall mysqld [root@www ~]$ ps -ef|grep mysql root 18116 17514 0 09:57 pts/1 00:00:00 grep mysql [root@www ~]$
啟動(dòng) mysqld ,現(xiàn)在執(zhí)行多次啟動(dòng)命令都沒有問題。
[root@www ~]$ service mysql start Starting MySQL. SUCCESS! [root@www ~]$ [root@www ~]$ [root@www ~]$ [root@www ~]$ [root@www ~]$ service mysql start Starting MySQL SUCCESS! [root@www ~]$
前面 www.err 文件中顯示的 error: 11 到底是什么,看下:
[root@www ~]$ perror 11 OS error code 11: Resource temporarily unavailable [root@www ~]$ [root@www ~]$
如有疑問請(qǐng)留言或者到本站社區(qū)交流討論,感謝閱讀,希望能幫助到大家,謝謝大家對(duì)本站的支持!
相關(guān)文章
JMeter對(duì)MySQL數(shù)據(jù)庫進(jìn)行壓力測(cè)試的實(shí)現(xiàn)步驟
本文主要介紹了JMeter對(duì)MySQL數(shù)據(jù)庫進(jìn)行壓力測(cè)試的實(shí)現(xiàn)步驟,文中通過示例代碼介紹的非常詳細(xì),具有一定的參考價(jià)值,感興趣的小伙伴們可以參考一下2022-01-01Sql Server數(shù)據(jù)庫遠(yuǎn)程連接訪問設(shè)置詳情
這篇文章主要介紹了Sql Server數(shù)據(jù)庫遠(yuǎn)程連接訪問設(shè)置詳情,文章圍繞主題展開詳細(xì)的內(nèi)容戒殺,具有一定的參考價(jià)值,需要的小伙伴可以參考一下2022-09-09mysql SKIP-NAME-RESOLVE 錯(cuò)誤的使用時(shí)機(jī)造成用戶權(quán)限
新加的一臺(tái)服務(wù)器,連接內(nèi)網(wǎng)中的一臺(tái)mysql服務(wù)器的時(shí)候,經(jīng)常出現(xiàn)超時(shí)。2011-06-06MySQL數(shù)據(jù)庫執(zhí)行Update卡死問題的解決方法
最近開發(fā)的時(shí)候debug到一條update的sql語句時(shí)程序就不動(dòng)了,然后我就在plsql上試了一下,發(fā)現(xiàn)plsql一直在顯示正在執(zhí)行,等了好久也不出結(jié)果,下面這篇文章主要給大家介紹了關(guān)于MySQL數(shù)據(jù)庫執(zhí)行Update卡死問題的解決方法,需要的朋友可以參考下2022-05-05