MYSQL不断崩溃

MYSQL不断崩溃,mysql,innodb,Mysql,Innodb,早些时候我已经修复了mysql,它一直崩溃。我所做的是停止mysql服务器,并删除了ib_logfile1和ib_logfile0。编辑了my etc/mysql/my.cnf,并将大小从32m调整为64m这就是my.cnf的样子 # INNODB # innodb_flush_method = O_DIRECT innodb_log_files_in_group = 2 innodb_log_file_size = 64M innodb_fl

早些时候我已经修复了mysql,它一直崩溃。我所做的是停止mysql服务器,并删除了ib_logfile1和ib_logfile0。编辑了my etc/mysql/my.cnf,并将大小从32m调整为64m这就是my.cnf的样子

# INNODB #
innodb_flush_method            = O_DIRECT
innodb_log_files_in_group      = 2
innodb_log_file_size           = 64M
innodb_flush_log_at_trx_commit = 1
innodb_file_per_table          = 1
innodb_buffer_pool_size        = 8M
过了一会儿,它又坠毁了。由于这个错误

140304 22:25:05 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
140304 22:25:34 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
140304 22:25:34 [Note] Plugin 'FEDERATED' is disabled.
140304 22:25:34  InnoDB: Initializing buffer pool, size = 8.0M
140304 22:25:34  InnoDB: Completed initialization of buffer pool
140304 22:25:34  InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 64 MB
InnoDB: Database physically writes the file full: wait...
140304 22:25:34  InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 64 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
140304 22:25:35  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
140304 22:25:35  InnoDB: Started; log sequence number 0 44556
140304 22:25:35 [Warning] 'user' entry 'root@sqldb' ignored in --skip-name-resolve mode.
140304 22:25:35 [Note] Event Scheduler: Loaded 0 events
140304 22:25:35 [Note] /usr/sbin/mysqld: ready for connections.

有什么建议可以解决这个问题吗?

MySQL启动后粘贴的是日志。开始之前的消息会有用得多嗯,问题是当我启动sql时没有错误,只是在启动之后出现错误,