標籤:databases atomic orm cuda waiting uil ... 方案 enc
ps -ef|grep mysql
發現裡邊沒有mysql進程,於是進行重啟。
service mysqld start報錯
查看錯誤記錄檔
tail -100 /usr/local/mysql/var/iZ11yohng9aZ.err(主機名稱.err)
180223 15:31:51 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/var180223 15:31:51 InnoDB: The InnoDB memory heap is disabled180223 15:31:51 InnoDB: Mutexes and rw_locks use GCC atomic builtins180223 15:31:51 InnoDB: Compressed tables use zlib 1.2.3180223 15:31:51 InnoDB: Initializing buffer pool, size = 16.0M180223 15:31:51 InnoDB: Completed initialization of buffer pool180223 15:31:51 InnoDB: highest supported file format is Barracuda.180223 15:31:51 InnoDB: Waiting for the background threads to start180223 15:31:52 InnoDB: 5.5.42 started; log sequence number 106443096/usr/local/mysql/bin/mysqld: File ‘./mysql-bin.000901‘ not found (Errcode: 2)180223 15:31:52 [ERROR] Failed to open log (file ‘./mysql-bin.000901‘, errno 2)180223 15:31:52 [ERROR] Could not open log file180223 15:31:52 [ERROR] Can‘t init tc log180223 15:31:52 [ERROR] Aborting180223 15:31:52 InnoDB: Starting shutdown...180223 15:31:53 InnoDB: Shutdown completed; log sequence number 106443096180223 15:31:53 [Note] /usr/local/mysql/bin/mysqld: Shutdown complete180223 15:31:53 mysqld_safe mysqld from pid file /usr/local/mysql/var/iZ11yohng9aZ.pid ended
可以看到,錯誤記錄檔中出現的錯誤資訊: Failed to open log (file ‘./mysql-bin.000901‘, errno 2)
於是嘗試解決方案如下:
cd /usr/local/mysql/var/cp mysql-bin.index mysql-bin.index.bak(備份)vi mysql-bin.index刪除其中的mysql-bin.000901
然後進行重啟,mysql啟動成功
Mysql啟動報錯解決方案:Failed to open log (file './mysql-bin.000901', errno 2)