• Welcome to Tux Reports: Where Penguins Fly. We hope you find the topics varied, interesting, and worthy of your time. Please become a member and join in the discussions.

MAMP Pro Crash

LPH

Flight Director
Flight Instructor
I just spent the last 2 hours trying to recover from a crash after upgrading MAMP Pro. The error log showed the lines below.

Code:
2017-04-08 09:14:41 4730 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_table_stats uses space ID: 1 at filepath: ./mysql/innodb_table_stats.ibd. Cannot open tablespace wordpress/wp_commentmeta which uses space ID: 1 at filepath: ./wordpress/wp_commentmeta.ibd
2017-04-08 09:14:41 7fffe0d073c0  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_commentmeta.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.
170408 09:14:41 mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended

The fix is actually very easy.

1. Open the my.conf
File >> Edit Template >> MySQL (my.conf)

2. In [mysqld] section, add the following line:
innodb_force_recovery = 1

3. Save and restart the server
 
Top