2016-12-16 150 views
-3

我在我的Mac(OS Sierra 10.12.1)上安装了MAMP并且工作正常。我正在用Eclipse开发Moodle并使用GIt。几天后我无法启动MySQL,我认为这是由于MySQL服务器中的一些问题。无法在MAP(Mac)中启动MySQL

我重新安装了MAMP并再次正常工作。现在,我遇到了同样的问题,无法启动MySQL。我认为与GIT有关系,因为我删除或更改了一些存储库。我已经复制了MySQL错误报告。

我尝试过建议像杀Kill MySql处理器,但没有帮助。

161216 10:37:23 mysqld_safe Starting mysqld daemon with databases from /Applications/MAMP/db/mysql56

2016-12-16 10:37:23 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).

2016-12-16 10:37:23 0 [Note] /Applications/MAMP/Library/bin/mysqld (mysqld 5.6.33) starting as process 6013 ...

2016-12-16 10:37:23 6013 [Warning] Setting lower_case_table_names=2 because file system for /Applications/MAMP/db/mysql56/ is case insensitive

2016-12-16 10:37:23 6013 [Note] Plugin 'FEDERATED' is disabled.

2016-12-16 10:37:23 6013 [Note] InnoDB: Using atomics to ref count buffer pool pages

2016-12-16 10:37:23 6013 [Note] InnoDB: The InnoDB memory heap is disabled

2016-12-16 10:37:23 6013 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2016-12-16 10:37:23 6013 [Note] InnoDB: Memory barrier is not used

2016-12-16 10:37:23 6013 [Note] InnoDB: Compressed tables use zlib 1.2.8

2016-12-16 10:37:23 6013 [Note] InnoDB: Using CPU crc32 instructions

2016-12-16 10:37:23 6013 [Note] InnoDB: Initializing buffer pool, size = 128.0M

2016-12-16 10:37:23 6013 [Note] InnoDB: Completed initialization of buffer pool

2016-12-16 10:37:23 6013 [Note] InnoDB: Highest supported file format is Barracuda.

2016-12-16 10:37:23 6013 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 7705227 in the ib_logfiles!

2016-12-16 10:37:23 6013 [Note] InnoDB: Database was not shutdown normally!

2016-12-16 10:37:23 6013 [Note] InnoDB: Starting crash recovery. 2016-12-16 10:37:23 6013 [Note] InnoDB: Reading tablespace information from the .ibd files... 2016-12-16 10:37:23 6013 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace moodle/mdl_config_plugins uses space ID: 2 at filepath: ./moodle/mdl_config_plugins.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: ./mysql/innodb_index_stats.ibd

2016-12-16 10:37:23 7fffe235b3c0 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_index_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.
161216 10:37:23 mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended

+1

嗨,我解决了这个问题,许多职位的帮助。 1)停止MAMP 2)创建的my.cnf在应用程序中的文件/ MAMP/conf文件夹 3)粘贴此内容 的[mysqld] 默认存储引擎= InnoDB的 innodb的 innodb_force_recovery = 1 5)重新开始MAMP 现在Sqlserver启动了 6)我评论了所有使用#的行(可能是第6步没有必要) –

回答

1

我通过很多帖子的帮助解决了这个问题。

1)停止MAMP

2)创建的my.cnf在应用程序中的文件/ MAMP/conf文件夹

3)粘贴此内容

的[mysqld]

默认存储 - 引擎= InnoDB

innodb

innodb_f orce_recovery = 1

5)重启MAMP
现在sqlserver的开始

6)然后,我得到了错误“无法写入数据库”,当我运行的Web应用程序,然后我做了7步和解决。

7)我评论了所有使用#

+0

什么是“第7步”? – brs14ku