Mamp不會啓動mysql服務器（mac）

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

這意味着你的一個表損壞了。奇怪的是，這經常發生在機器崩潰之後。 這是我如何固定它：

1. 開放的my.cnf（在MAMP>文件>編輯模板>的MySQL）
2. 添加一行：innodb_force_recovery = 1個
3. 保存和啓動服務器

表格可能仍然會被破壞，但是應該啓動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

我能夠通過導航到/ Applications/MAMP/db/mysql56並刪除我創建的數據庫的文件夾來獲得此工作。您可能可以將它們移動到桌面並重新導入它們，但我不需要它，因此我只是將其刪除，然後重新啓動並運行。

Answer 3

所有的MAMP數據庫都存儲在/Library/Application Support/appsolute/MAMP PRO/db/mysql56/單獨的文件夾中。根據您的錯誤日誌，存在./wordpress/wp_term_taxonomy.ib的問題 - 也就是數據庫中的term_taxonomywordpress。解決這個問題的一種方法是簡單地刪除該數據庫的所有痕跡 - 我希望你有一個來自它被損壞之前的副本來恢復它。這是如何刪除它：

1. 退出MAMP服務器。

2. 刪除數據庫文件夾及其內容 - 在你的情況下，數據庫名稱是WordPress的：

   $ rm -r /Library/Application\ Support/appsolute/MAMP\ PRO/db/mysql56/wordpress 
   

3. 刪除三個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 
   

4. 啓動MAMP服務器。