MySQL MAMPが動作しない

Question

MAMPに問題があります。このようなポートを設定します： Apache：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の変更方法がわかりません.PhotoMyAdminではRaceHistoryという名前のデータベースを作成しました。 私はMySQLのポートを変更しようとしましたが、私は3300,3306とランダムなポートで試しました.3300でそれは一瞬働きましたが、もう一度クラッシュします。 あなたは考えがあれば！ ありがとうございました！ （そして私の英語のために申し訳ありません）

EDIT：私は/ MAMP/binに行き、私はsh start.shを実行します、それはApacheのために起動しますが、mysqlのために私はこれを持っています：

私はtmp/mysqlに行ったので、mysql.pidファイルはありませんでした。

Answer 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.