【问题标题】:MAMP Pro 3.2 upgrade now MySQL fails to start (Yosemite)MAMP Pro 3.2 现在升级 MySQL 无法启动 (Yosemite)
【发布时间】:2015-05-01 23:11:26
【问题描述】:

我刚刚将 MAMP PRO 升级到 3.2,在重新启动服务器时出现 MySQL 错误。 MAMP 然后弹出一条消息,说有升级到 3.2.1 - 我希望他们发现了这个错误并且 3.2.1 包含了修复.. 没有这样的运气。

升级到 3.2.1,在启动服务器时出现 MySQL 启动失败错误。日志中的详细信息如下:

150501 17:58:26 mysqld_safe Starting mysqld daemon with databases from /Library/Application Support/appsolute/MAMP PRO/db/mysql
150501 17:58:27 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
150501 17:58:27 [Warning] Setting lower_case_table_names=2 because file system for /Library/Application Support/appsolute/MAMP PRO/db/mysql/ is case insensitive
150501 17:58:27 [Note] Plugin 'FEDERATED' is disabled.
150501 17:58:27 InnoDB: The InnoDB memory heap is disabled
150501 17:58:27 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150501 17:58:27 InnoDB: Compressed tables use zlib 1.2.3
150501 17:58:27 InnoDB: Initializing buffer pool, size = 128.0M
150501 17:58:27 InnoDB: Completed initialization of buffer pool
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.
150501 17:58:27  InnoDB: Retrying to lock the first data file
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

我去 Mamp Pro 论坛阅读和发帖,但他们指示每个人都在这里发布支持问题。好的。为付费的商业产品获取免费支持系统的好方法。

【问题讨论】:

    标签: mysql upgrade mamp-pro


    【解决方案1】:

    经过更多挖掘后,我发现了另一个帖子,这很有效:

    killall -9 mysqld 
    

    从终端运行它..它将杀死所有 MySQL 实例,这就是(明显)导致失败的原因..它已经在运行了?!?!

    【讨论】:

      猜你喜欢
      • 2019-05-16
      • 1970-01-01
      • 1970-01-01
      • 2014-09-28
      • 2015-11-08
      • 1970-01-01
      • 2014-12-24
      • 1970-01-01
      • 2018-05-08
      相关资源
      最近更新 更多