无法启动/停止/重新启动服务: MySQL守护进程启动失败

Question

当尝试重新启动mysqld服务时，我得到的是这个erroe:无法启动/停止/重新启动服务: MySQL守护进程启动失败。

有人知道怎么解决吗？我正在运行centos6.5，从我所看到的情况来看，我缺少了文件: /var/lib/mysql/mysql.sock

mysql错误日志

    140707 12:09:29 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
140707 12:09:29 [Note] libgovernor.so not found
140707 12:09:29 [Warning] option 'innodb-buffer-pool-size': signed value 2097152 adjusted to 5242880
140707 12:09:29 [Warning] option 'innodb-additional-mem-pool-size': signed value 512000 adjusted to 524288
140707 12:09:29 [Note] Plugin 'FEDERATED' is disabled.
140707 12:09:29 InnoDB: The InnoDB memory heap is disabled
140707 12:09:29 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140707 12:09:29 InnoDB: Compressed tables use zlib 1.2.3
140707 12:09:29 InnoDB: Using Linux native AIO
140707 12:09:29  InnoDB: Warning: io_setup() failed with EAGAIN. Will make 5 attempts before giving up.
InnoDB: Warning: io_setup() attempt 1 failed.
InnoDB: Warning: io_setup() attempt 2 failed.
InnoDB: Warning: io_setup() attempt 3 failed.
InnoDB: Warning: io_setup() attempt 4 failed.
InnoDB: Warning: io_setup() attempt 5 failed.
140707 12:09:31  InnoDB: Error: io_setup() failed with EAGAIN after 5 attempts.
InnoDB: You can disable Linux Native AIO by setting innodb_use_native_aio = 0 in my.cnf
140707 12:09:31 InnoDB: Fatal error: cannot initialize AIO sub-system
140707 12:09:31 [ERROR] Plugin 'InnoDB' init function returned error.
140707 12:09:31 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
140707 12:09:31 [ERROR] Unknown/unsupported storage engine: InnoDB
140707 12:09:31 [ERROR] Aborting

140707 12:09:31 [Note] /usr/libexec/mysqld: Shutdown complete

140707 12:09:31 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

谢谢你的回答，但我需要从备份中恢复

Answer 1

这似乎是AIO无法被设置的一个问题。这可能是因为：

1. 配额空间限制:您是否为要启动MySQL的用户设置配额？试着看看quota -s
2. 通过HD的空间限制:也许你已经没有空间了。看看df -h，看看是否有任何驱动器接近容量。
3. 权限问题:您试图重新启动服务的用户是否具有适当的权限？
4. 配置更改:您最近更改配置了吗？作为一个测试，尝试在my.cnf中恢复您的配置。您可能还想尝试在innodb_use_native_aio = 0中禁用AIO，但这只是一个解决办法。
5. 数据库损坏:由于数据库损坏，我还没有看到这个错误弹出，但我认为这是可能的。

希望这能有所帮助。