《MYSQL數據庫mysql禁用日志后無法啟動問題怎么解》要點：
本文介紹了MYSQL數據庫mysql禁用日志后無法啟動問題怎么解，希望對您有用。如果有疑問，可以聯系我們。

mysql數據庫啟動不了,查看錯誤日志：
/usr/sbin/mysqld: File './mysql-bin.000003' not found (Errcode: 2)
140319 10:49:22 [ERROR] Failed to open log (file './mysql-bin.000003', errno 2)
140319 10:49:22 [ERROR] Could not open log file
140319 10:49:22 [ERROR] Can't init tc log
140319 10:49:22 [ERROR] AbortingMYSQL實例

140319 10:49:22? InnoDB: Starting shutdown...
140319 10:49:27? InnoDB: Shutdown completed; log sequence number 0 2154633517
140319 10:49:27 [Note] /usr/sbin/mysqld: Shutdown completeMYSQL實例

140319 10:49:27 mysqld_safe mysqld from pid file /var/lib/mysql/richinfo-dev2.pid ended
140319 10:59:48 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
140319 10:59:48 [Note] Plugin 'FEDERATED' is disabled.
140319 10:59:48? InnoDB: Initializing buffer pool, size = 256.0M
140319 10:59:48? InnoDB: Completed initialization of buffer pool
140319 10:59:48? InnoDB: Started; log sequence number 0 2154633517
/usr/sbin/mysqld: File './mysql-bin.000003' not found (Errcode: 2)
140319 10:59:48 [ERROR] Failed to open log (file './mysql-bin.000003', errno 2)
140319 10:59:48 [ERROR] Could not open log file
140319 10:59:48 [ERROR] Can't init tc log
140319 10:59:48 [ERROR] AbortingMYSQL實例

140319 10:59:48? InnoDB: Starting shutdown...
140319 10:59:54? InnoDB: Shutdown completed; log sequence number 0 2154633517
140319 10:59:54 [Note] /usr/sbin/mysqld: Shutdown completeMYSQL實例

140319 10:59:54 mysqld_safe mysqld from pid file /var/lib/mysql/richinfo-dev2.pid endedMYSQL實例

顯示找不到日志文件/mysql-bin.000003,在linux操作系統查看該文件確實不存在,繼續查看mysql啟動參數文件/etc/my.cnf
#log-bin=mysql-bin
原來是mysql數據庫禁用了日志功能,可能是mysql-bin.index文件沒有刪除導致的,在系統中查看該文件確實存在,將其刪除后,再次啟動數據庫,數據庫能正常啟動了.MYSQL實例

轉載請注明本頁網址：
http://www.snjht.com/jiaocheng/6454.html