MAMP Pro Mysql启动实拍 log中抛出以下信息
171116 10:04:18 mysqld_safe Logging to '/Applications/MAMP/logs/mysql_error.log'.
171116 10:04:18 mysqld_safe Starting mysqld daemon with databases from /Library/Application Support/appsolute/MAMP PRO/db/mysql56
2017-11-16 10:04:19 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-11-16 10:04:19 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2017-11-16 10:04:19 0 [Note] /Applications/MAMP/Library/bin/mysqld (mysqld 5.6.35) starting as process 1876 ...
2017-11-16 10:04:19 1876 [Warning] Setting lower_case_table_names=2 because file system for /Library/Application Support/appsolute/MAMP PRO/db/mysql56/ is case insensitive
2017-11-16 10:04:19 1876 [Note] Plugin 'FEDERATED' is disabled.
2017-11-16 10:04:19 1876 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-11-16 10:04:19 1876 [Note] InnoDB: The InnoDB memory heap is disabled
2017-11-16 10:04:19 1876 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-11-16 10:04:19 1876 [Note] InnoDB: Memory barrier is not used
2017-11-16 10:04:19 1876 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-11-16 10:04:19 1876 [Note] InnoDB: Using CPU crc32 instructions
2017-11-16 10:04:19 1876 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-11-16 10:04:19 1876 [Note] InnoDB: Completed initialization of buffer pool
2017-11-16 10:04:19 1876 [Note] InnoDB: Highest supported file format is Barracuda.
2017-11-16 10:04:19 1876 [Note] InnoDB: The log sequence numbers 1634512 and 1634512 in ibdata files do not match the log sequence number 1634522 in the ib_logfiles!
2017-11-16 10:04:19 1876 [Note] InnoDB: Database was not shutdown normally!
2017-11-16 10:04:19 1876 [Note] InnoDB: Starting crash recovery.
2017-11-16 10:04:19 1876 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-11-16 10:04:19 1876 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace blog/user uses space ID: 1 at filepath: ./blog/user.ibd. Cannot open tablespace mysql/innodb_table_stats which uses space ID: 1 at filepath: ./mysql/innodb_table_stats.ibd
2017-11-16 10:04:19 7fffb1cd83c0 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/innodb_table_stats.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.
查询ps -ef|grep mysqld 没有对应的启动进程，
看到出错信息应该是InnoDB下出现的问题:innodb_table_stats.ibd
InnoDB: Error: could not open single-table tablespace file ./mysql/innodb_table_stats.ibd InnoDB: We do not continue the crash recovery, because the table may become
所以编写mysql的配置文件my.cnf(打开MAMP -->File->Edit Template-->MySQL(my.cnf))
在mysqld下
添加如下内容
innodb_force_recovery = 1
重启mysql，成功解决，然后删除innodb_force_recovery = 1再次重新启动MySQL
网友评论