Исправляем ошибку «mamp pro InnoDB: Operating system error number 2 in a file operation.«, которая появляется при запуске MySQL в программе MAMP PRO.
Ошибки подобного рода могут возникнуть, когда база данных MySQL была завершена не надлежащим способом. Например, когда работал MAMP PRO и неожиданно перезагрузился компьютер.
У меня ошибка выглядела следующим образом:
170817 16:06:20 mysqld_safe Starting mysqld daemon with databases from /Library/Application Support/appsolute/MAMP PRO/db/mysql56
2017-08-17 16:06:21 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-08-17 16:06:21 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2017-08-17 16:06:21 0 [Note] /Applications/MAMP/Library/bin/mysqld (mysqld 5.6.35) starting as process 43367 ...
2017-08-17 16:06:21 43367 [Warning] Setting lower_case_table_names=2 because file system for /Library/Application Support/appsolute/MAMP PRO/db/mysql56/ is case insensitive
2017-08-17 16:06:21 43367 [Note] Plugin 'FEDERATED' is disabled.
2017-08-17 16:06:21 43367 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-08-17 16:06:21 43367 [Note] InnoDB: The InnoDB memory heap is disabled
2017-08-17 16:06:21 43367 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-08-17 16:06:21 43367 [Note] InnoDB: Memory barrier is not used
2017-08-17 16:06:21 43367 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-08-17 16:06:21 43367 [Note] InnoDB: Using CPU crc32 instructions
2017-08-17 16:06:21 43367 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-08-17 16:06:21 43367 [Note] InnoDB: Completed initialization of buffer pool
2017-08-17 16:06:21 43367 [Note] InnoDB: Highest supported file format is Barracuda.
2017-08-17 16:06:21 43367 [Note] InnoDB: The log sequence numbers 32097731 and 32097731 in ibdata files do not match the log sequence number 32219971 in the ib_logfiles!
2017-08-17 16:06:21 43367 [Note] InnoDB: Database was not shutdown normally!
2017-08-17 16:06:21 43367 [Note] InnoDB: Starting crash recovery.
2017-08-17 16:06:21 43367 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-08-17 16:06:21 43367 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_worker_info uses space ID: 5 at filepath: ./mysql/slave_worker_info.ibd. Cannot open tablespace wordpress/wp_term_taxonomy which uses space ID: 5 at filepath: ./wordpress/wp_term_taxonomy.ibd
2017-08-17 16:06:21 7fffa15bd3c0 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
InnoDB: Error: could not open single-table tablespace file ./wordpress/wp_term_taxonomy.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
170817 16:06:21 mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended
Для исправления заходим в меню программы:
File -> Edit Template -> MySql (my.cnf)
Меню будет недоступно, если вы выбрали через настройки скрывать программу MAMP PRO в Dock (Mac OS).
В открывшемся файле находим строчку:
Раскомментируем её и поменяем значение на следующее:
Таким образом при запуске базы данных MySQL будет принудительно восстанавливаться InnoDB (системы управления базы данными).
Теперь запускаем MySQL через программу MAMP PRO. Всё должно запуститься успешно.
Снова заходим в файл настроек MySQL и приводим значения, которые были по умолчанию. Можно не возвращать значения обратно, если ошибка возникает часто.
