与MAMP发生Freak MySql错误

时间:2013-03-05 14:31:31

标签: macos mamp mysql

  • 我设置了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

5 个答案:

答案 0 :(得分:59)

只需搜索"活动监控器"应用于MAC并搜索任何名为mysql的任务并结束它。 然后重新启动MAMP它会工作。希望它可以帮到某人。

答案 1 :(得分:8)

结束活动监视器应用程序中的任何mysqlmysqld任务(或其他)。

答案 2 :(得分:5)

如果您无法使用活动监视器杀死它们, 在终端中做 /<\/blockquote>([\s\S]*?)<\/div>/
第二列是进程ID,您可以使用(如果它是1234)来停止它 $ ps aux | grep mysqld

答案 3 :(得分:0)

我通过杀死mysqld进程解决了这个问题:

要杀死Linux上的所有mysqld进程

# killall mysqld mysqld_safe

至少等待10秒钟,使其干净地关闭。 现在,运行此命令以检查是否还剩下一些mysqld进程?

# ps aux | grep mysqld

如果您仍然可以看到除运行此命令之外的内容:

killall -9 mysqld mysqld_safe

这将杀死所有mysqld进程。

答案 4 :(得分:0)

只需重新启动您的电脑,对我来说就解决了