MySQL 不是从 MAMP 开始
MySQL Not starting with MAMP
我知道这可能看起来重复,但我正在努力。
我设法启动并 运行 Apache 和 MySQL 使用 MAMP 的一个会话。再来一次,MySQL不会启动
我在 Stack 上尝试过各种答案。重新安装/移动目录/确保更新。我还没有做的一件事是重命名 'ib_logfile' - 因为它们不存在!
有人有什么建议吗?
2017-09-23 20:44:46 7fffa5a753c0 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
InnoDB: Error: could not open single-table tablespace file ./mysql/slave_worker_info.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
170923 20:44:46 mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended
到目前为止我已经开始工作了 - 我将 Mamp 中的 Mysql 文件夹的权限更改为读取和写入以及所有包含的文件夹,它似乎可以工作。
- 转到 /Applications/MAMP/tmp/mysql/ 并添加新文件 mysql.pid
- 重新启动 mamp
我知道这可能看起来重复,但我正在努力。
我设法启动并 运行 Apache 和 MySQL 使用 MAMP 的一个会话。再来一次,MySQL不会启动
我在 Stack 上尝试过各种答案。重新安装/移动目录/确保更新。我还没有做的一件事是重命名 'ib_logfile' - 因为它们不存在!
有人有什么建议吗?
2017-09-23 20:44:46 7fffa5a753c0 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
InnoDB: Error: could not open single-table tablespace file ./mysql/slave_worker_info.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
170923 20:44:46 mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended
到目前为止我已经开始工作了 - 我将 Mamp 中的 Mysql 文件夹的权限更改为读取和写入以及所有包含的文件夹,它似乎可以工作。
- 转到 /Applications/MAMP/tmp/mysql/ 并添加新文件 mysql.pid
- 重新启动 mamp