Question

我有麻烦并且正在运行（wordpress）并且没有任何问题。然后服务器突然停机，并没有再次启动。他们是关于这个主题的其他一些主题，但我还没有弄明白。我已经确认没有mysql进程....这是我的mysql_error_log：

161201 01:04:22 mysqld_safe Starting mysqld daemon with databases from /Applications/MAMP/db/mysql56
2016-12-01 01:04:23 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2016-12-01 01:04:23 0 [Note] /Applications/MAMP/Library/bin/mysqld (mysqld 5.6.33) starting as process 49478 ...
2016-12-01 01:04:23 49478 [Warning] Setting lower_case_table_names=2 because file system for /Applications/MAMP/db/mysql56/ is case insensitive
2016-12-01 01:04:23 49478 [Note] Plugin 'FEDERATED' is disabled.
2016-12-01 01:04:23 49478 [Note] InnoDB: Using atomics to ref count buffer pool pages
2016-12-01 01:04:23 49478 [Note] InnoDB: The InnoDB memory heap is disabled
2016-12-01 01:04:23 49478 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-12-01 01:04:23 49478 [Note] InnoDB: Memory barrier is not used
2016-12-01 01:04:23 49478 [Note] InnoDB: Compressed tables use zlib 1.2.8
2016-12-01 01:04:23 49478 [Note] InnoDB: Using CPU crc32 instructions
2016-12-01 01:04:23 49478 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2016-12-01 01:04:23 49478 [Note] InnoDB: Completed initialization of buffer pool
2016-12-01 01:04:23 49478 [Note] InnoDB: Highest supported file format is Barracuda.
2016-12-01 01:04:23 49478 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 9969064 in the ib_logfiles!
2016-12-01 01:04:23 49478 [Note] InnoDB: Database was not shutdown normally!
2016-12-01 01:04:23 49478 [Note] InnoDB: Starting crash recovery.
2016-12-01 01:04:23 49478 [Note] InnoDB: Reading tablespace information from the .ibd files...
2016-12-01 01:04:23 49478 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_worker_info uses space ID: 5 at filepath: ./mysql/slave_worker_info.ibd. Cannot open tablespace wordpress/wp_term_taxonomy which uses space ID: 5 at filepath: ./wordpress/wp_term_taxonomy.ibd
2016-12-01 01:04:23 7fffc52a43c0  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 ./wordpress/wp_term_taxonomy.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.
161201 01:04:23 mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended

Answer 1

这意味着您的一个表已损坏。奇怪的是，这经常发生在机器崩溃时。这就是我修复它的方法：

打开my.cnf（在MAMP＆gt;文件＆gt;编辑模板＆gt; MySQL）
添加以下行：innodb_force_recovery = 1
保存并启动服务器

该表可能仍会被破坏，但应该启动mysql。这意味着您可能必须替换您的表：wp_term_taxonomy

注意：如果innodb_force_recovery = 1不起作用，请尝试使用数字： innodb_force_recovery = 2（等）但要谨慎行事。这是MySQL对此设置的警告： https://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html

Answer 2

所有MAMP数据库都存储在 / Library / Application Support / appsolute / MAMP PRO / db / mysql56 / 的单独文件夹中。根据您的错误日志， ./ wordpress / wp_term_taxonomy.ib 存在问题 - 即数据库 wordpress term_taxonomy >。解决这个问题的一种方法是简单地删除该数据库的所有痕迹 - 我希望你在它被破坏之前有一个副本来恢复它。这是你删除它的方式：

退出MAMP服务器。
删除数据库文件夹及其内容 - 在您的情况下，数据库名称为 wordpress ：
```
$ rm -r /Library/Application\ Support/appsolute/MAMP\ PRO/db/mysql56/wordpress
```

删除三个InnoDB文件 ib_logfile0 ， ib_logfile1 和 ibdata1 。不要害怕;下次从MAMP中启动MySQL时，将创建新的副本。

$ rm /Library/Application\ Support/appsolute/MAMP\ PRO/db/mysql56/ib_logfile0
$ rm /Library/Application\ Support/appsolute/MAMP\ PRO/db/mysql56/ib_logfile1
$ rm /Library/Application\ Support/appsolute/MAMP\ PRO/db/mysql56/ibdata1

启动MAMP服务器。

Answer 3

我能够通过导航到/ Applications / MAMP / db / mysql56并删除我创建的数据库的文件夹来实现此功能。您可以将它们移动到桌面并重新导入它们，但我不需要它，所以我只是将其删除然后重新启动它就可以了。

Mamp不会启动mysql服务器（mac）

3 个答案: