gpt4 book ai didi

mysql - MAMP Pro 3.2 升级现在 MySQL 启动失败(Yosemite)

转载 作者:行者123 更新时间:2023-11-29 02:56:45 25 4
gpt4 key购买 nike

我刚刚将 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 论坛阅读和发帖,..但他们指示每个人都在这里发布支持问题。好的。为付费商业产品获得免费支持系统的好方法。

最佳答案

经过更多挖掘后,我发现了另一篇文章,这很有效:

killall -9 mysqld 

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

关于mysql - MAMP Pro 3.2 升级现在 MySQL 启动失败(Yosemite),我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/29996447/

25 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com