MySQL 无法在 AMPPS OS X 上启动

Posted 2023-02-23

【中文标题】MySQL 无法在 AMPPS OS X 上启动

【英文标题】：MySQL doesn't starts on AMPPS OS X

【发布时间】：2014-02-12 23:49:32

【问题描述】：

我在使用 AMPPS 启动 mysql 时遇到问题。我正在使用 OS X Maverics 和最新版本的 Ammps。在系统崩溃并重新启动后，我无法启动 mysql。

mysql.err

2014-01-22 18:12:41 398 [Note] Plugin 'FEDERATED' is disabled.
2014-01-22 18:12:41 398 [Note] InnoDB: The InnoDB memory heap is disabled
2014-01-22 18:12:41 398 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2014-01-22 18:12:41 398 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-01-22 18:12:41 398 [Note] InnoDB: Not using CPU crc32 instructions
2014-01-22 18:12:41 398 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-01-22 18:12:41 398 [Note] InnoDB: Completed initialization of buffer pool
2014-01-22 18:12:41 398 [Note] InnoDB: Highest supported file format is Barracuda.
2014-01-22 18:12:41 398 [Note] InnoDB: The log sequence numbers 1252002624 and 1252002624 in ibdata files do not match the log sequence number 1252003161 in the ib_logfiles!
2014-01-22 18:12:41 398 [Note] InnoDB: Database was not shutdown normally!
2014-01-22 18:12:41 398 [Note] InnoDB: Starting crash recovery.
2014-01-22 18:12:41 398 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-01-22 18:12:41 398 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace analytics/backlinks uses space ID: 1 at filepath: ./analytics/backlinks.ibd. Cannot open tablespace mysql/innodb_table_stats which uses space ID: 1 at filepath: ./mysql/innodb_table_stats.ibd
2014-01-22 18:12:41 a08901a8 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.

请帮帮我。我在 DB 中有非常重要的文件。

【参考方案1】：

解决！

Open AMPPS Application -> MySQL Tab -> Configuration.

在[mysqld] 部分，添加以下行： innodb_force_recovery = 1

保存文件并尝试启动 MySQL

删除刚刚添加的那一行并保存。

【讨论】：

而不是删除推荐将是更好的选择，因为每次更新后问题再次出现。

只是为了补充 Halis 的观点 - 注释是一种很好的方式 - 只需在行前添加一个哈希：#.

在 OS X Yosemite 崩溃后也会发生这种情况，但这些步骤会对其进行排序。

我的mac运行yosemite随机死机然后关机，当我重新打开它时我无法打开mySQL。将此行添加到 Config file 就像一个魅力！

【参考方案2】：

所以我遇到了类似的问题，我尝试过的是：-

find / -name mysql

从上述命令的输出中删除所有搜索结果。然后执行以下操作：-

brew uninstall mysql
brew clean

然后重新启动您的机器一次，然后使用以下命令再次安装：-

brew install mysql

P.S：我收到此错误 error，所以我无法备份我的数据库，但我的数据库中没有太多重要数据，所以我还是删除了它