【问题标题】:MySQL MAMP doesn't workMySQL MAMP 不起作用
【发布时间】:2017-02-27 17:59:40
【问题描述】:

我遇到了 MAMP 问题,我将端口设置如下: 阿帕奇:8888 MySQL:8889 但 MySQL 不起作用。所以我阅读了 mysql_error_log.err 文件,我有这个:

> 161018 14:21:12 mysqld_safe Starting mysqld daemon with databases from /Applications/MAMP/db/mysql56
2016-10-18 14:21:13 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2016-10-18 14:21:13 0 [Note] /Applications/MAMP/Library/bin/mysqld (mysqld 5.6.28) starting as process 6728 ...
2016-10-18 14:21:13 6728 [Warning] Setting lower_case_table_names=2 because file system for /Applications/MAMP/db/mysql56/ is case insensitive
2016-10-18 14:21:13 6728 [Note] Plugin 'FEDERATED' is disabled.
2016-10-18 14:21:13 6728 [Note] InnoDB: Using atomics to ref count buffer pool pages
2016-10-18 14:21:13 6728 [Note] InnoDB: The InnoDB memory heap is disabled
2016-10-18 14:21:13 6728 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-10-18 14:21:13 6728 [Note] InnoDB: Memory barrier is not used
2016-10-18 14:21:13 6728 [Note] InnoDB: Compressed tables use zlib 1.2.8
2016-10-18 14:21:13 6728 [Note] InnoDB: Using CPU crc32 instructions
2016-10-18 14:21:13 6728 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2016-10-18 14:21:13 6728 [Note] InnoDB: Completed initialization of buffer pool
2016-10-18 14:21:13 6728 [Note] InnoDB: Highest supported file format is Barracuda.
2016-10-18 14:21:13 6728 [Note] InnoDB: The log sequence numbers 1600607 and 1600607 in ibdata files do not match the log sequence number 1605546 in the ib_logfiles!
2016-10-18 14:21:13 6728 [Note] InnoDB: Database was not shutdown normally!
2016-10-18 14:21:13 6728 [Note] InnoDB: Starting crash recovery.
2016-10-18 14:21:13 6728 [Note] InnoDB: Reading tablespace information from the .ibd files...
2016-10-18 14:21:13 6728 [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 racehistory/users which uses space ID: 1 at filepath: ./racehistory/users.ibd
2016-10-18 14:21:13 7fff77000000  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 ./racehistory/users.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.
161018 14:21:13 mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended

但我不明白这是什么。但是我在这一行看到了

> InnoDB: Error: could not open single-table tablespace file ./racehistory/users.ibd

这不是我的数据库名称,我的数据库名称是 RaceHistory。也许问题就在这里,但在这种情况下,我不知道如何更改 MySQL,在 PHPmyAdmin 中我创建了一个名为:RaceHistory 的数据库。 我尝试更改 MySQL 的端口,我尝试使用 3300、3306 和随机端口,使用 3300 它工作了一会儿,它再次崩溃。 所以如果你有任何想法! 谢谢 ! (对不起我的英语)

编辑:我尝试通过终端启动 apache 和 mysql,所以我去了 /MAMP/bin 并执行了 sh start.sh,它为 apache 启动,但对于 mysql,我有这个:

161018 15:45:39 mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended

所以我去了 tmp/mysql 却没有 mysql.pid 文件!

【问题讨论】:

  • `InnoDB:错误表示系统找不到指定的路径。
  • 是的,但是 users.ibd 在比赛历史的文件夹中!

标签: mysql mamp


【解决方案1】:

您的错误消息提供了一些很好的线索,下一步该做什么。

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 ./racehistory/users.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.

【讨论】:

  • 我删除了我的文件 users.ibd 一次,它起作用了,但是当我再次创建表时,同样的错误又回来了,所以我不想再次删除我的文件。我尝试更改我的 users.ibd 的权限 chmod a+rw 并且没有任何变化。
猜你喜欢
  • 2014-04-14
  • 2012-06-06
  • 2017-09-02
  • 1970-01-01
  • 1970-01-01
  • 1970-01-01
  • 1970-01-01
  • 2023-03-20
  • 2015-03-27
相关资源
最近更新 更多