Question

我在本地开发并使用Mamp Pro。基本上MySQL无法启动，这是错误日志中的错误消息：

知道如何解决这个问题吗？

2017-03-02 00:39:08 9518 [Note] Plugin 'FEDERATED' is disabled.
2017-03-02 00:39:08 9518 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-03-02 00:39:08 9518 [Note] InnoDB: The InnoDB memory heap is disabled
2017-03-02 00:39:08 9518 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-03-02 00:39:08 9518 [Note] InnoDB: Memory barrier is not used
2017-03-02 00:39:08 9518 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-03-02 00:39:08 9518 [Note] InnoDB: Using CPU crc32 instructions
2017-03-02 00:39:08 9518 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-03-02 00:39:08 9518 [Note] InnoDB: Completed initialization of buffer pool
2017-03-02 00:39:08 9518 [Note] InnoDB: Highest supported file format is Barracuda.
2017-03-02 00:39:08 9518 [Note] InnoDB: Log scan progressed past the checkpoint lsn 663573438
2017-03-02 00:39:08 9518 [Note] InnoDB: Database was not shutdown normally!
2017-03-02 00:39:08 9518 [Note] InnoDB: Starting crash recovery.
2017-03-02 00:39:08 9518 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-03-02 00:39:08 9518 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace affiliate_blog_1_old/wpab1_7_woocommerce_order_itemmeta uses space ID: 367 at filepath: ./affiliate_blog_1_old/wpab1_7_woocommerce_order_itemmeta.ibd. Cannot open tablespace freshwp/freshwp_wfblocksadv which uses space ID: 367 at filepath: ./freshwp/freshwp_wfblocksadv.ibd
2017-03-02 00:39:08 7fff7b652000  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 ./freshwp/freshwp_wfblocksadv.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.
170302 00:39:08 mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended

从上面的代码看，错误似乎是：

2017-03-02 00:39:08 9518 [错误] InnoDB：尝试打开以前打开的表空间。

上一个表空间affiliate_blog_1_old / wpab1_7_woocommerce_order_itemmeta 使用空间ID：367 在文件路径：./ owniliate_blog_1_old/wpab1_7_woocommerce_order_itemmeta.ibd。

无法打开使用空格ID：367的表空间freshwp / freshwp_wfblocksadv 在filepath：./ frreshwp /freshwp_wfblocksadv.ibd

Answer 1

最近遇到类似的问题，开发本地w / MAMP。日志包括“数据库未正常关闭”，此后的类似错误消息以及建议。以下是解决它的步骤：

在MAMP中停止服务器
导航到WP DB的.idb文件 - 如果使用MAMP，应该在〜/ Library / Application Support / appsolute / MAMP PRO / db / mysql56 / [yourdbname] /
将.bk（或任何无法识别的扩展名）添加到.idb文件名的末尾
在MAMP中启动服务器。如果您查看日志，您将看到一堆与未找到.idb文件相关的错误消息，但至少MySQL应该启动。
在MAMP中停止服务器
从.idb文件名中删除.bk（或您使用的任何内容）
在MAMP中启动服务器 - 此时应该全部设置。

尚未对数据库做过多少工作，所以愿意丢失数据甚至重新安装MAMP;如果您的情况不同，最好先将您的db目录备份到.zip文件，这样如果没有运气，您可以稍后尝试其他方法。

希望这有帮助。

...

更新：
使用以下内容更新步骤3和6的速度更快：
3.在某个地方创建一个临时文件夹;选择所有.idb文件并将其移动到该文件夹中 6.将文件从步骤2移回原始文件夹。 ....

MySQL的问题 - InnoDB：文件操作中的操作系统错误号2

1 个答案: