Pour info je joins le contenu du fichier mysql_error.log ( c'est du chinois pour moi)
170305 17:38:20 mysqld_safe Starting mysqld daemon with databases from /Library/Application Support/appsolute/MAMP PRO/db/mysql56
2017-03-05 17:38:21 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-03-05 17:38:21 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2017-03-05 17:38:21 0 [Note] /Applications/MAMP/Library/bin/mysqld (mysqld 5.6.34) starting as process 11123 ...
2017-03-05 17:38:21 11123 [Warning] Setting lower_case_table_names=2 because file system for /Library/Application Support/appsolute/MAMP PRO/db/mysql56/ is case insensitive
2017-03-05 17:38:21 11123 [Note] Plugin 'FEDERATED' is disabled.
2017-03-05 17:38:21 11123 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-03-05 17:38:21 11123 [Note] InnoDB: The InnoDB memory heap is disabled
2017-03-05 17:38:21 11123 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-03-05 17:38:21 11123 [Note] InnoDB: Memory barrier is not used
2017-03-05 17:38:21 11123 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-03-05 17:38:21 11123 [Note] InnoDB: Not using CPU crc32 instructions
2017-03-05 17:38:21 11123 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-03-05 17:38:21 11123 [Note] InnoDB: Completed initialization of buffer pool
2017-03-05 17:38:21 11123 [Note] InnoDB: Highest supported file format is Barracuda.
2017-03-05 17:38:21 11123 [Note] InnoDB: The log sequence numbers 9207278 and 9207278 in ibdata files do not match the log sequence number 9245475 in the ib_logfiles!
2017-03-05 17:38:21 11123 [Note] InnoDB: Database was not shutdown normally!
2017-03-05 17:38:21 11123 [Note] InnoDB: Starting crash recovery.
2017-03-05 17:38:21 11123 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-03-05 17:38:21 11123 [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 sophrolib_db/wp_term_taxonomy which uses space ID: 5 at filepath: ./sophrolib_db/wp_term_taxonomy.ibd
2017-03-05 17:38:21 7fff7eac8000 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 ./sophrolib_db/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.
170305 17:38:21 mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended
170305 17:39:24 mysqld_safe Starting mysqld daemon with databases from /Library/Application Support/appsolute/MAMP PRO/db/mysql56
2017-03-05 17:39:24 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-03-05 17:39:24 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2017-03-05 17:39:24 0 [Note] /Applications/MAMP/Library/bin/mysqld (mysqld 5.6.34) starting as process 12210 ...
2017-03-05 17:39:24 12210 [Warning] Setting lower_case_table_names=2 because file system for /Library/Application Support/appsolute/MAMP PRO/db/mysql56/ is case insensitive
2017-03-05 17:39:24 12210 [Note] Plugin 'FEDERATED' is disabled.
2017-03-05 17:39:24 12210 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-03-05 17:39:24 12210 [Note] InnoDB: The InnoDB memory heap is disabled
2017-03-05 17:39:24 12210 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-03-05 17:39:24 12210 [Note] InnoDB: Memory barrier is not used
2017-03-05 17:39:24 12210 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-03-05 17:39:24 12210 [Note] InnoDB: Not using CPU crc32 instructions
2017-03-05 17:39:24 12210 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-03-05 17:39:24 12210 [Note] InnoDB: Completed initialization of buffer pool
2017-03-05 17:39:24 12210 [Note] InnoDB: Highest supported file format is Barracuda.
2017-03-05 17:39:24 12210 [Note] InnoDB: The log sequence numbers 9207278 and 9207278 in ibdata files do not match the log sequence number 9245475 in the ib_logfiles!
2017-03-05 17:39:24 12210 [Note] InnoDB: Database was not shutdown normally!
2017-03-05 17:39:24 12210 [Note] InnoDB: Starting crash recovery.
2017-03-05 17:39:24 12210 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-03-05 17:39:24 12210 [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 sophrolib_db/wp_term_taxonomy which uses space ID: 5 at filepath: ./sophrolib_db/wp_term_taxonomy.ibd
2017-03-05 17:39:24 7fff7eac8000 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 ./sophrolib_db/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.
170305 17:39:24 mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended
170305 17:40:17 mysqld_safe Starting mysqld daemon with databases from /Library/Application Support/appsolute/MAMP PRO/db/mysql56
2017-03-05 17:40:18 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-03-05 17:40:18 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2017-03-05 17:40:18 0 [Note] /Applications/MAMP/Library/bin/mysqld (mysqld 5.6.34) starting as process 13257 ...
2017-03-05 17:40:18 13257 [Warning] Setting lower_case_table_names=2 because file system for /Library/Application Support/appsolute/MAMP PRO/db/mysql56/ is case insensitive
2017-03-05 17:40:18 13257 [Note] Plugin 'FEDERATED' is disabled.
2017-03-05 17:40:18 13257 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-03-05 17:40:18 13257 [Note] InnoDB: The InnoDB memory heap is disabled
2017-03-05 17:40:18 13257 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-03-05 17:40:18 13257 [Note] InnoDB: Memory barrier is not used
2017-03-05 17:40:18 13257 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-03-05 17:40:18 13257 [Note] InnoDB: Not using CPU crc32 instructions
2017-03-05 17:40:18 13257 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-03-05 17:40:18 13257 [Note] InnoDB: Completed initialization of buffer pool
2017-03-05 17:40:18 13257 [Note] InnoDB: Highest supported file format is Barracuda.
2017-03-05 17:40:18 13257 [Note] InnoDB: The log sequence numbers 9207278 and 9207278 in ibdata files do not match the log sequence number 9245475 in the ib_logfiles!
2017-03-05 17:40:18 13257 [Note] InnoDB: Database was not shutdown normally!
2017-03-05 17:40:18 13257 [Note] InnoDB: Starting crash recovery.
2017-03-05 17:40:18 13257 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-03-05 17:40:18 13257 [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 sophrolib_db/wp_term_taxonomy which uses space ID: 5 at filepath: ./sophrolib_db/wp_term_taxonomy.ibd
2017-03-05 17:40:18 7fff7eac8000 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 ./sophrolib_db/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.
170305 17:40:18 mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended
170305 17:42:55 mysqld_safe Starting mysqld daemon with databases from /Library/Application Support/appsolute/MAMP PRO/db/mysql56
2017-03-05 17:42:55 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-03-05 17:42:55 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2017-03-05 17:42:55 0 [Note] /Applications/MAMP/Library/bin/mysqld (mysqld 5.6.34) starting as process 15462 ...
2017-03-05 17:42:55 15462 [Warning] Setting lower_case_table_names=2 because file system for /Library/Application Support/appsolute/MAMP PRO/db/mysql56/ is case insensitive
2017-03-05 17:42:55 15462 [Note] Plugin 'FEDERATED' is disabled.
2017-03-05 17:42:55 15462 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-03-05 17:42:55 15462 [Note] InnoDB: The InnoDB memory heap is disabled
2017-03-05 17:42:55 15462 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-03-05 17:42:55 15462 [Note] InnoDB: Memory barrier is not used
2017-03-05 17:42:55 15462 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-03-05 17:42:55 15462 [Note] InnoDB: Not using CPU crc32 instructions
2017-03-05 17:42:55 15462 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-03-05 17:42:55 15462 [Note] InnoDB: Completed initialization of buffer pool
2017-03-05 17:42:56 15462 [Note] InnoDB: Highest supported file format is Barracuda.
2017-03-05 17:42:56 15462 [Note] InnoDB: The log sequence numbers 9207278 and 9207278 in ibdata files do not match the log sequence number 9245475 in the ib_logfiles!
2017-03-05 17:42:56 15462 [Note] InnoDB: Database was not shutdown normally!
2017-03-05 17:42:56 15462 [Note] InnoDB: Starting crash recovery.
2017-03-05 17:42:56 15462 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-03-05 17:42:56 15462 [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 sophrolib_db/wp_term_taxonomy which uses space ID: 5 at filepath: ./sophrolib_db/wp_term_taxonomy.ibd
2017-03-05 17:42:56 7fff7eac8000 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 ./sophrolib_db/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.
170305 17:42:56 mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended
170305 17:52:50 mysqld_safe Starting mysqld daemon with databases from /Library/Application Support/appsolute/MAMP PRO/db/mysql56
2017-03-05 17:52:50 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-03-05 17:52:50 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2017-03-05 17:52:50 0 [Note] /Applications/MAMP/Library/bin/mysqld (mysqld 5.6.34) starting as process 23775 ...
2017-03-05 17:52:50 23775 [Warning] Setting lower_case_table_names=2 because file system for /Library/Application Support/appsolute/MAMP PRO/db/mysql56/ is case insensitive
2017-03-05 17:52:50 23775 [Note] Plugin 'FEDERATED' is disabled.
2017-03-05 17:52:50 23775 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-03-05 17:52:50 23775 [Note] InnoDB: The InnoDB memory heap is disabled
2017-03-05 17:52:50 23775 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-03-05 17:52:50 23775 [Note] InnoDB: Memory barrier is not used
2017-03-05 17:52:50 23775 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-03-05 17:52:50 23775 [Note] InnoDB: Not using CPU crc32 instructions
2017-03-05 17:52:50 23775 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-03-05 17:52:50 23775 [Note] InnoDB: Completed initialization of buffer pool
2017-03-05 17:52:50 23775 [Note] InnoDB: Highest supported file format is Barracuda.
2017-03-05 17:52:50 23775 [Note] InnoDB: The log sequence numbers 9207278 and 9207278 in ibdata files do not match the log sequence number 9245475 in the ib_logfiles!
2017-03-05 17:52:50 23775 [Note] InnoDB: Database was not shutdown normally!
2017-03-05 17:52:50 23775 [Note] InnoDB: Starting crash recovery.
2017-03-05 17:52:50 23775 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-03-05 17:52:50 23775 [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 sophrolib_db/wp_term_taxonomy which uses space ID: 5 at filepath: ./sophrolib_db/wp_term_taxonomy.ibd
2017-03-05 17:52:50 7fff7eac8000 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 ./sophrolib_db/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.
170305 17:52:50 mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended
170305 17:53:40 mysqld_safe Starting mysqld daemon with databases from /Library/Application Support/appsolute/MAMP PRO/db/mysql56
2017-03-05 17:53:41 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-03-05 17:53:41 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2017-03-05 17:53:41 0 [Note] /Applications/MAMP/Library/bin/mysqld (mysqld 5.6.34) starting as process 24887 ...
2017-03-05 17:53:41 24887 [Warning] Setting lower_case_table_names=2 because file system for /Library/Application Support/appsolute/MAMP PRO/db/mysql56/ is case insensitive
2017-03-05 17:53:41 24887 [Note] Plugin 'FEDERATED' is disabled.
2017-03-05 17:53:41 24887 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-03-05 17:53:41 24887 [Note] InnoDB: The InnoDB memory heap is disabled
2017-03-05 17:53:41 24887 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-03-05 17:53:41 24887 [Note] InnoDB: Memory barrier is not used
2017-03-05 17:53:41 24887 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-03-05 17:53:41 24887 [Note] InnoDB: Not using CPU crc32 instructions
2017-03-05 17:53:41 24887 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-03-05 17:53:41 24887 [Note] InnoDB: Completed initialization of buffer pool
2017-03-05 17:53:41 24887 [Note] InnoDB: Highest supported file format is Barracuda.
2017-03-05 17:53:41 24887 [Note] InnoDB: The log sequence numbers 9207278 and 9207278 in ibdata files do not match the log sequence number 9245475 in the ib_logfiles!
2017-03-05 17:53:41 24887 [Note] InnoDB: Database was not shutdown normally!
2017-03-05 17:53:41 24887 [Note] InnoDB: Starting crash recovery.
2017-03-05 17:53:41 24887 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-03-05 17:53:41 24887 [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 sophrolib_db/wp_term_taxonomy which uses space ID: 5 at filepath: ./sophrolib_db/wp_term_taxonomy.ibd
2017-03-05 17:53:41 7fff7eac8000 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 ./sophrolib_db/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.
170305 17:53:41 mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended
170306 05:47:28 mysqld_safe Starting mysqld daemon with databases from /Library/Application Support/appsolute/MAMP PRO/db/mysql56
170306 05:47:28 mysqld_safe Starting mysqld daemon with databases from /Library/Application Support/appsolute/MAMP PRO/db/mysql56
2017-03-06 05:47:28 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-03-06 05:47:28 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2017-03-06 05:47:28 0 [Note] /Applications/MAMP/Library/bin/mysqld (mysqld 5.6.34) starting as process 79919 ...
2017-03-06 05:47:28 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-03-06 05:47:28 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2017-03-06 05:47:28 0 [Note] /Applications/MAMP/Library/bin/mysqld (mysqld 5.6.34) starting as process 79912 ...
2017-03-06 05:47:28 79919 [Warning] Setting lower_case_table_names=2 because file system for /Library/Application Support/appsolute/MAMP PRO/db/mysql56/ is case insensitive
2017-03-06 05:47:28 79912 [Warning] Setting lower_case_table_names=2 because file system for /Library/Application Support/appsolute/MAMP PRO/db/mysql56/ is case insensitive
2017-03-06 05:47:28 79919 [Note] Plugin 'FEDERATED' is disabled.
2017-03-06 05:47:28 79912 [Note] Plugin 'FEDERATED' is disabled.
2017-03-06 05:47:28 79912 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-03-06 05:47:28 79912 [Note] InnoDB: The InnoDB memory heap is disabled
2017-03-06 05:47:28 79912 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-03-06 05:47:28 79912 [Note] InnoDB: Memory barrier is not used
2017-03-06 05:47:28 79912 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-03-06 05:47:28 79919 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-03-06 05:47:28 79919 [Note] InnoDB: The InnoDB memory heap is disabled
2017-03-06 05:47:28 79919 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-03-06 05:47:28 79919 [Note] InnoDB: Memory barrier is not used
2017-03-06 05:47:28 79919 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-03-06 05:47:28 79919 [Note] InnoDB: Not using CPU crc32 instructions
2017-03-06 05:47:28 79912 [Note] InnoDB: Not using CPU crc32 instructions
2017-03-06 05:47:28 79912 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-03-06 05:47:28 79919 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-03-06 05:47:28 79912 [Note] InnoDB: Completed initialization of buffer pool
2017-03-06 05:47:28 79919 [Note] InnoDB: Completed initialization of buffer pool
2017-03-06 05:47:28 79919 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2017-03-06 05:47:28 79919 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-03-06 05:47:28 79919 [Note] InnoDB: Retrying to lock the first data file
2017-03-06 05:47:28 79912 [Note] InnoDB: Highest supported file format is Barracuda.
2017-03-06 05:47:28 79912 [Note] InnoDB: The log sequence numbers 9207278 and 9207278 in ibdata files do not match the log sequence number 9245475 in the ib_logfiles!
2017-03-06 05:47:28 79912 [Note] InnoDB: Database was not shutdown normally!
2017-03-06 05:47:28 79912 [Note] InnoDB: Starting crash recovery.
2017-03-06 05:47:28 79912 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-03-06 05:47:28 79912 [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 sophrolib_db/wp_term_taxonomy which uses space ID: 5 at filepath: ./sophrolib_db/wp_term_taxonomy.ibd
2017-03-06 05:47:28 7fff7eac8000 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 ./sophrolib_db/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.
170306 05:47:28 mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended
2017-03-06 05:47:29 79919 [Note] InnoDB: Highest supported file format is Barracuda.
2017-03-06 05:47:29 79919 [Note] InnoDB: The log sequence numbers 9207278 and 9207278 in ibdata files do not match the log sequence number 9245475 in the ib_logfiles!
2017-03-06 05:47:29 79919 [Note] InnoDB: Database was not shutdown normally!
2017-03-06 05:47:29 79919 [Note] InnoDB: Starting crash recovery.
2017-03-06 05:47:29 79919 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-03-06 05:47:29 79919 [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 sophrolib_db/wp_term_taxonomy which uses space ID: 5 at filepath: ./sophrolib_db/wp_term_taxonomy.ibd
2017-03-06 05:47:29 7fff7eac8000 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 ./sophrolib_db/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.
170306 05:47:29 mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended
