无法启动/停止/重新启动服务:MySQL Daemon 启动失败

无法启动/停止/重新启动服务:MySQL Daemon 启动失败

当尝试重新启动 mysqld 服务时,我收到此错误:无法启动/停止/重新启动服务:MySQL 守护进程无法启动。

有人知道如何解决吗?我正在运行 centos 6.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

谢谢您的回答,但我需要从备份中恢复它

答案1

这似乎是无法设置 AIO 的问题。可能是因为:

  1. 通过配额进行空间限制:您是否为启动 MySQL 的用户设置了配额?尝试查看quota -s
  2. 高清空间限制:也许您的空间不足。查看df -h是否有驱动器接近容量上限。
  3. 权限问题:您尝试重新启动服务的用户是否具有适当的权限?
  4. 配置更改:您最近更改过配置吗?作为测试,请尝试在 中恢复您的配置my.cnf。您可能还想尝试使用 禁用 AIO,innodb_use_native_aio = 0但这实际上只是一种解决方法。
  5. 数据库损坏:我还没有看到由于数据库损坏而弹出此错误,但我认为这是一种可能性。

希望这可以帮助。

相关内容