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] Aborting

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 complete

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] Aborting

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 complete

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

显示找不到日志文件/mysql-bin.000003，在linux操作系统查看该文件确实不存在，继续查看mysql启动参数文件/etc/my.cnf
#log-bin=mysql-bin
原来是mysql数据库禁用了日志功能，可能是mysql-bin.index文件没有删除导致的，在系统中查看该文件确实存在，将其删除后，再次启动数据库，数据库能正常启动了。

您可能感兴趣的文章：
mysql禁用日志后无法启动问题怎么解
centos mysql不能随主机启动怎么办
mysql启动错误报1067错误怎么解决
清除mysql的log-bin日志的方案
解决开启bin-log日志mysql报错的问题
Linux Apache Mysql PHP典型配置
Win7系统无线怎么开启?windows 7 无线开启方法图解
自动清理binlog日志与手动删除binlog日志的方法
mysql设置自动清理binlog日志的方法
mysql无法启动出现1067错误问题(图文)