当我在MAMP上选择“启动服务器”时，MySQL服务器将无法启动

Question

我是一个完全菜鸟，所以请向我尽可能简单地解释！ 注意：我正在使用Mac（OS X YOSEMITE）并运行MAMP。

我曾经去过Apache服务器和MySQL，但是几个小时前，计算机崩溃了，重新启动计算机后，MySQL服务器将无法加载。

我尝试直接进入localhost：8888 / phpMyAdmin，但产生错误：

“＃2002-没有这样的文件或目录-服务器没有响应（或未正确配置本地服务器的套接字）。

“ mysqli_real_connect（）：（HY000 / 2002）：没有这样的文件或目录”

这是最新的错误代码（我认为）：

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

我该怎么办？

Answer 1

“试图打开以前打开的表空间。” -闻起来像其中之一：

• 有两个MySQL副本，两个都试图运行。 仔细搜索运行mysqld的服务。
• 不知何故，文件之间（可能是.ibd文件）之间存在硬链接。