MySQL無法啟動的解決辦法
更新時間:2017年09月11日 09:41:02 作者:codingstandards
這篇文章主要介紹了MySQL無法啟動的解決辦法的相關(guān)資料,希望通過本文大家能解決數(shù)據(jù)庫不能啟動的問題,需要的朋友可以參考下
MySQL無法啟動的解決辦法
MySQL無法啟動
在停止mysql之后,執(zhí)行了一些操作(如修改主機名),重新啟動 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 ~]$
實在是啟動不了,看一下日志:/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 并沒有停下來。
強制終止 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 ~]$
啟動 mysqld ,現(xiàn)在執(zhí)行多次啟動命令都沒有問題。
[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ū)交流討論,感謝閱讀,希望能幫助到大家,謝謝大家對本站的支持!
相關(guān)文章
Django+mysql配置與簡單操作數(shù)據(jù)庫實例代碼
這篇文章主要介紹了Django+mysql配置與簡單操作數(shù)據(jù)庫實例,需要的朋友可以參考下2017-07-07
MySQL [Warning] TIMESTAMP with implicit&
本文介紹了MySQL中常見的報錯信息及其解決方法,主要包括TIMESTAMP with implicit DEFAULT value is deprecated、ERROR_FOR_DIVISION_BY_ZERO和NO_ZERO_DATE/NO_ZERO_IN_DATE等報錯信息,以及對應的配置文件設置和sql_mode修改方法,感興趣的朋友一起看看吧2025-02-02

