2
我剛剛將MAMP PRO升級到了3.2，並且在重新啓動服務器時我收到了MySQL錯誤。然後MAMP彈出消息說升級到了3.2.1 - 我希望他們發現了這個bug，並且3.2.1包含了修復。沒有這樣的運氣。現在MAMP Pro 3.2升級MySQL無法啓動（優勝美地）
升級到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
我去毫安專業論壇，閱讀和發佈，..但他們指揮大家在這裏發表支持問題。尼斯。獲得付費商業產品免費支持系統的好方法。