13
  • 我设置了 MAMP Pro。在此之前，我设置并删除了 MAMP 和 XAMPP。我疯狂地删除了前两个的所有文件。从那时起，Apache 没有在 Mamp 默认端口 8888 上运行，并且 - MySql 根本没有运行。
  • 一行写着“检查 mysqld 进程是否已经运行”我检查了它，但它不是！- 这是错误日志。
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 35
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 35
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 35
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
130305 19:49:08  InnoDB: Unable to open the first data file
InnoDB: Error in opening ./ibdata1
130305 19:49:08  InnoDB: Operating system error number 35 in a file operation.
InnoDB: Error number 35 means 'Resource temporarily unavailable'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html
130305 19:49:08 InnoDB: Could not open or create data files.
130305 19:49:08 InnoDB: If you tried to add new data files, and it failed here,
130305 19:49:08 InnoDB: you should now edit innodb_data_file_path in my.cnf back
130305 19:49:08 InnoDB: to what it was, and remove the new ibdata files InnoDB created
130305 19:49:08 InnoDB: in this failed attempt. InnoDB only wrote those files full of
130305 19:49:08 InnoDB: zeros, but did not yet use them in any way. But be careful: do not
130305 19:49:08 InnoDB: remove old data files which contain your precious data!
130305 19:49:08 [ERROR] Plugin 'InnoDB' init function returned error.
130305 19:49:08 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
130305 19:49:08 [ERROR] Unknown/unsupported storage engine: InnoDB
130305 19:49:08 [ERROR] Aborting

130305 19:49:08 [Note] /Applications/MAMP/Library/bin/mysqld: Shutdown complete

130305 19:49:08 mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended
4

5 回答 5

60

只需在 MAC 上搜索“活动监视器”应用程序并搜索任何名为 mysql 的任务并结束它。然后重启 MAMP 就可以了。希望它可以帮助某人。

于 2014-03-18T04:50:09.743 回答
8

结束Activity Monitor应用程序中的任何mysql或mysqld任务（或其他） 。

于 2014-05-12T17:04:21.717 回答
6

如果你不能用Activity Monitor杀死它们，在终端做
$ ps aux | grep mysqld
第二列是进程ID，你可以用（如果是1234）停止它
$ kill 1234

于 2016-03-22T04:10:50.820 回答
0

我通过 kill mysqld 进程解决了这个问题：

要杀死Linux 上的所有 mysqld 进程：

# killall mysqld mysqld_safe

至少等待 10 秒钟，以便它干净地关闭。现在，运行这个命令来检查是否还有一些 mysqld 进程仍然存在？

# ps aux | grep mysqld

如果您仍然能够看到更多内容，请运行以下命令：

killall -9 mysqld mysqld_safe

这将杀死所有 mysqld 进程。

于 2020-02-22T02:55:27.157 回答
0

只需重新启动您的电脑，这为我解决了它

于 2020-11-16T12:05:16.410 回答