I was doing some WordPress stuff, everything worked fine. But the next day, the MYSQL could not be started. I am not familiar with such things, so I just reinstalled the XAMPP. I had to create a new database in order to continue working with WordPress. It worked fine until I turned off my computer... The following day MYSQL could not be started again. I hope you guys can help me out.
- Code: Select all
11:32:58 [mysql] Error: MySQL shutdown unexpectedly.
11:32:58 [mysql] This may be due to a blocked port, missing dependencies,
11:32:58 [mysql] improper privileges, a crash, or a shutdown by another method.
11:32:58 [mysql] Press the Logs button to view error logs and check
11:32:58 [mysql] the Windows Event Viewer for more clues
11:32:58 [mysql] If you need more help, copy and post this
11:32:58 [mysql] entire log window on the forums
- Code: Select all
2013-07-27 16:43:36 7020 [Note] Plugin 'FEDERATED' is disabled.
2013-07-27 16:43:36 16c0 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2013-07-27 16:43:36 7020 [Note] InnoDB: The InnoDB memory heap is disabled
2013-07-27 16:43:36 7020 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-07-27 16:43:36 7020 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-07-27 16:43:36 7020 [Note] InnoDB: Not using CPU crc32 instructions
2013-07-27 16:43:36 7020 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-07-27 16:43:36 7020 [Note] InnoDB: Completed initialization of buffer pool
2013-07-27 16:43:36 7020 [Note] InnoDB: The first specified data file C:\xampp\mysql\data\ibdata1 did not exist: a new database to be created!
2013-07-27 16:43:36 7020 [Note] InnoDB: Setting file C:\xampp\mysql\data\ibdata1 size to 10 MB
2013-07-27 16:43:36 7020 [Note] InnoDB: Database physically writes the file full: wait...
2013-07-27 16:43:36 7020 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile101 size to 5 MB
2013-07-27 16:43:37 7020 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile1 size to 5 MB
2013-07-27 16:43:37 7020 [Note] InnoDB: Renaming log file C:\xampp\mysql\data\ib_logfile101 to C:\xampp\mysql\data\ib_logfile0
2013-07-27 16:43:37 7020 [Warning] InnoDB: New log files created, LSN=45781
2013-07-27 16:43:37 7020 [Note] InnoDB: Doublewrite buffer not found: creating new
2013-07-27 16:43:37 7020 [Note] InnoDB: Doublewrite buffer created
2013-07-27 16:43:39 7020 [Note] InnoDB: 128 rollback segment(s) are active.
2013-07-27 16:43:39 7020 [Warning] InnoDB: Creating foreign key constraint system tables.
2013-07-27 16:43:39 7020 [Note] InnoDB: Foreign key constraint system tables created
2013-07-27 16:43:39 7020 [Note] InnoDB: Creating tablespace and datafile system tables.
2013-07-27 16:43:39 7020 [Note] InnoDB: Tablespace and datafile system tables created.
2013-07-27 16:43:39 7020 [Note] InnoDB: Waiting for purge to start
2013-07-27 16:43:39 7020 [Note] InnoDB: 5.6.11 started; log sequence number 0
2013-07-27 16:43:39 7020 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: 8b342d4d-f6c2-11e2-869b-e81132c12440.
2013-07-27 16:43:39 7020 [Note] Server hostname (bind-address): '*'; port: 3306
2013-07-27 16:43:39 7020 [Note] IPv6 is available.
2013-07-27 16:43:39 7020 [Note] - '::' resolves to '::';
2013-07-27 16:43:39 7020 [Note] Server socket created on IP: '::'.
2013-07-27 16:43:39 7020 [Warning] InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2013-07-27 16:43:39 7020 [Warning] Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.
2013-07-27 16:43:39 7020 [Warning] InnoDB: Cannot open table mysql/slave_worker_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2013-07-27 16:43:39 7020 [Warning] InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2013-07-27 16:43:39 7020 [Warning] Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.
2013-07-27 16:43:39 7020 [Note] Event Scheduler: Loaded 0 events
2013-07-27 16:43:39 7020 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.11' socket: '' port: 3306 MySQL Community Server (GPL)
2013-07-27 17:16:37 1c84 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-07-27 17:16:37 1c84 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-07-27 17:16:37 1c84 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-07-27 17:16:37 1c84 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-07-27 17:16:37 1c84 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_options" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2013-07-27 17:16:37 1c84 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-07-27 17:16:37 1c84 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_users" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2013-07-27 17:16:37 1c84 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-07-27 17:16:37 1c84 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_usermeta" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2013-07-27 17:16:37 1c84 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-07-27 17:16:37 1c84 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_terms" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2013-07-27 17:16:37 1c84 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-07-27 17:16:37 1c84 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_term_taxonomy" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2013-07-27 17:16:37 1c84 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-07-27 17:16:37 1c84 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_posts" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2013-07-27 17:16:37 1c84 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-07-27 17:16:37 1c84 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_term_relationships" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2013-07-27 17:16:37 1c84 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-07-27 17:16:37 1c84 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_comments" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2013-07-27 17:16:37 1c84 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-07-27 17:16:37 1c84 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_postmeta" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2013-07-27 17:16:47 3b4 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-07-27 17:16:47 3b4 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_options" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-07-27 17:16:49 1a34 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-07-27 17:16:49 1a34 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_commentmeta" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2013-07-27 17:16:49 1d14 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-07-27 17:16:49 1d14 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_commentmeta" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2013-07-27 17:16:51 3b4 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-07-27 17:16:51 3b4 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_posts" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-07-27 17:17:01 3b4 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-07-27 17:17:01 3b4 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_usermeta" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-07-27 17:17:11 3b4 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-07-27 17:17:11 3b4 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_options" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-07-27 17:23:39 3b4 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-07-27 17:23:39 3b4 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_postmeta" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-07-27 17:23:39 3b4 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-07-27 17:23:39 3b4 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_posts" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-07-28 11:07:31 7884 [Note] Plugin 'FEDERATED' is disabled.
2013-07-28 11:07:32 1544 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2013-07-28 11:07:32 7884 [Note] InnoDB: The InnoDB memory heap is disabled
2013-07-28 11:07:32 7884 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-07-28 11:07:32 7884 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-07-28 11:07:32 7884 [Note] InnoDB: Not using CPU crc32 instructions
2013-07-28 11:07:32 7884 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-07-28 11:07:32 7884 [Note] InnoDB: Completed initialization of buffer pool
2013-07-28 11:07:32 7884 [Note] InnoDB: Highest supported file format is Barracuda.
2013-07-28 11:07:32 7884 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2884023 in the ib_logfiles!
2013-07-28 11:07:32 7884 [Note] InnoDB: Database was not shutdown normally!
2013-07-28 11:07:32 7884 [Note] InnoDB: Starting crash recovery.
2013-07-28 11:07:32 7884 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-07-28 11:07:32 7884 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace wordpress/wp_terms which uses space ID: 3 at filepath: .\wordpress\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\wordpress\wp_terms.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.
2013-07-28 11:17:02 7832 [Note] Plugin 'FEDERATED' is disabled.
2013-07-28 11:17:02 1f4c InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2013-07-28 11:17:02 7832 [Note] InnoDB: The InnoDB memory heap is disabled
2013-07-28 11:17:02 7832 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-07-28 11:17:02 7832 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-07-28 11:17:02 7832 [Note] InnoDB: Not using CPU crc32 instructions
2013-07-28 11:17:02 7832 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-07-28 11:17:02 7832 [Note] InnoDB: Completed initialization of buffer pool
2013-07-28 11:17:03 7832 [Note] InnoDB: Highest supported file format is Barracuda.
2013-07-28 11:17:03 7832 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2884023 in the ib_logfiles!
2013-07-28 11:17:03 7832 [Note] InnoDB: Database was not shutdown normally!
2013-07-28 11:17:03 7832 [Note] InnoDB: Starting crash recovery.
2013-07-28 11:17:03 7832 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-07-28 11:17:03 7832 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace wordpress/wp_terms which uses space ID: 3 at filepath: .\wordpress\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\wordpress\wp_terms.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.
2013-07-28 11:19:49 6624 [Note] Plugin 'FEDERATED' is disabled.
2013-07-28 11:19:49 1148 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2013-07-28 11:19:49 6624 [Note] InnoDB: The InnoDB memory heap is disabled
2013-07-28 11:19:49 6624 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-07-28 11:19:49 6624 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-07-28 11:19:49 6624 [Note] InnoDB: Not using CPU crc32 instructions
2013-07-28 11:19:49 6624 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-07-28 11:19:49 6624 [Note] InnoDB: Completed initialization of buffer pool
2013-07-28 11:19:49 6624 [Note] InnoDB: Highest supported file format is Barracuda.
2013-07-28 11:19:49 6624 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2884023 in the ib_logfiles!
2013-07-28 11:19:49 6624 [Note] InnoDB: Database was not shutdown normally!
2013-07-28 11:19:49 6624 [Note] InnoDB: Starting crash recovery.
2013-07-28 11:19:49 6624 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-07-28 11:19:49 6624 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace wordpress/wp_terms which uses space ID: 3 at filepath: .\wordpress\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\wordpress\wp_terms.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.
2013-07-28 11:19:58 7128 [Note] Plugin 'FEDERATED' is disabled.
2013-07-28 11:19:58 18ec InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2013-07-28 11:19:58 7128 [Note] InnoDB: The InnoDB memory heap is disabled
2013-07-28 11:19:58 7128 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-07-28 11:19:58 7128 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-07-28 11:19:58 7128 [Note] InnoDB: Not using CPU crc32 instructions
2013-07-28 11:19:58 7128 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-07-28 11:19:58 7128 [Note] InnoDB: Completed initialization of buffer pool
2013-07-28 11:19:58 7128 [Note] InnoDB: Highest supported file format is Barracuda.
2013-07-28 11:19:58 7128 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2884023 in the ib_logfiles!
2013-07-28 11:19:58 7128 [Note] InnoDB: Database was not shutdown normally!
2013-07-28 11:19:58 7128 [Note] InnoDB: Starting crash recovery.
2013-07-28 11:19:58 7128 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-07-28 11:19:58 7128 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace wordpress/wp_terms which uses space ID: 3 at filepath: .\wordpress\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\wordpress\wp_terms.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.
2013-07-28 11:27:57 7276 [Note] Plugin 'FEDERATED' is disabled.
2013-07-28 11:27:57 1544 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2013-07-28 11:27:57 7276 [Note] InnoDB: The InnoDB memory heap is disabled
2013-07-28 11:27:57 7276 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-07-28 11:27:57 7276 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-07-28 11:27:57 7276 [Note] InnoDB: Not using CPU crc32 instructions
2013-07-28 11:27:57 7276 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-07-28 11:27:57 7276 [Note] InnoDB: Completed initialization of buffer pool
2013-07-28 11:27:57 7276 [Note] InnoDB: Highest supported file format is Barracuda.
2013-07-28 11:27:57 7276 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2884023 in the ib_logfiles!
2013-07-28 11:27:57 7276 [Note] InnoDB: Database was not shutdown normally!
2013-07-28 11:27:57 7276 [Note] InnoDB: Starting crash recovery.
2013-07-28 11:27:57 7276 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-07-28 11:27:57 7276 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace wordpress/wp_terms which uses space ID: 3 at filepath: .\wordpress\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\wordpress\wp_terms.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.
2013-07-28 11:32:47 940 [Note] Plugin 'FEDERATED' is disabled.
2013-07-28 11:32:47 cc8 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2013-07-28 11:32:47 940 [Note] InnoDB: The InnoDB memory heap is disabled
2013-07-28 11:32:47 940 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-07-28 11:32:47 940 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-07-28 11:32:47 940 [Note] InnoDB: Not using CPU crc32 instructions
2013-07-28 11:32:47 940 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-07-28 11:32:47 940 [Note] InnoDB: Completed initialization of buffer pool
2013-07-28 11:32:47 940 [Note] InnoDB: Highest supported file format is Barracuda.
2013-07-28 11:32:47 940 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2884023 in the ib_logfiles!
2013-07-28 11:32:47 940 [Note] InnoDB: Database was not shutdown normally!
2013-07-28 11:32:47 940 [Note] InnoDB: Starting crash recovery.
2013-07-28 11:32:47 940 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-07-28 11:32:47 940 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace wordpress/wp_terms which uses space ID: 3 at filepath: .\wordpress\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\wordpress\wp_terms.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.
2013-07-28 11:32:48 3444 [Note] Plugin 'FEDERATED' is disabled.
2013-07-28 11:32:48 1a58 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2013-07-28 11:32:48 3444 [Note] InnoDB: The InnoDB memory heap is disabled
2013-07-28 11:32:48 3444 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-07-28 11:32:48 3444 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-07-28 11:32:48 3444 [Note] InnoDB: Not using CPU crc32 instructions
2013-07-28 11:32:48 3444 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-07-28 11:32:48 3444 [Note] InnoDB: Completed initialization of buffer pool
2013-07-28 11:32:48 3444 [Note] InnoDB: Highest supported file format is Barracuda.
2013-07-28 11:32:48 3444 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2884023 in the ib_logfiles!
2013-07-28 11:32:48 3444 [Note] InnoDB: Database was not shutdown normally!
2013-07-28 11:32:48 3444 [Note] InnoDB: Starting crash recovery.
2013-07-28 11:32:48 3444 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-07-28 11:32:48 3444 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace wordpress/wp_terms which uses space ID: 3 at filepath: .\wordpress\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\wordpress\wp_terms.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.
2013-07-28 11:32:49 7244 [Note] Plugin 'FEDERATED' is disabled.
2013-07-28 11:32:49 1d9c InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2013-07-28 11:32:49 7244 [Note] InnoDB: The InnoDB memory heap is disabled
2013-07-28 11:32:49 7244 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-07-28 11:32:49 7244 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-07-28 11:32:49 7244 [Note] InnoDB: Not using CPU crc32 instructions
2013-07-28 11:32:49 7244 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-07-28 11:32:49 7244 [Note] InnoDB: Completed initialization of buffer pool
2013-07-28 11:32:49 7244 [Note] InnoDB: Highest supported file format is Barracuda.
2013-07-28 11:32:49 7244 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2884023 in the ib_logfiles!
2013-07-28 11:32:49 7244 [Note] InnoDB: Database was not shutdown normally!
2013-07-28 11:32:49 7244 [Note] InnoDB: Starting crash recovery.
2013-07-28 11:32:49 7244 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-07-28 11:32:49 7244 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace wordpress/wp_terms which uses space ID: 3 at filepath: .\wordpress\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\wordpress\wp_terms.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.
2013-07-28 11:32:49 8060 [Note] Plugin 'FEDERATED' is disabled.
2013-07-28 11:32:49 1a88 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2013-07-28 11:32:49 8060 [Note] InnoDB: The InnoDB memory heap is disabled
2013-07-28 11:32:49 8060 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-07-28 11:32:49 8060 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-07-28 11:32:49 8060 [Note] InnoDB: Not using CPU crc32 instructions
2013-07-28 11:32:49 8060 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-07-28 11:32:49 8060 [Note] InnoDB: Completed initialization of buffer pool
2013-07-28 11:32:49 8060 [Note] InnoDB: Highest supported file format is Barracuda.
2013-07-28 11:32:50 8060 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2884023 in the ib_logfiles!
2013-07-28 11:32:50 8060 [Note] InnoDB: Database was not shutdown normally!
2013-07-28 11:32:50 8060 [Note] InnoDB: Starting crash recovery.
2013-07-28 11:32:50 8060 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-07-28 11:32:50 8060 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace wordpress/wp_terms which uses space ID: 3 at filepath: .\wordpress\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\wordpress\wp_terms.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.
2013-07-28 11:32:50 4668 [Note] Plugin 'FEDERATED' is disabled.
2013-07-28 11:32:50 1bcc InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2013-07-28 11:32:50 4668 [Note] InnoDB: The InnoDB memory heap is disabled
2013-07-28 11:32:50 4668 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-07-28 11:32:50 4668 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-07-28 11:32:50 4668 [Note] InnoDB: Not using CPU crc32 instructions
2013-07-28 11:32:50 4668 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-07-28 11:32:50 4668 [Note] InnoDB: Completed initialization of buffer pool
2013-07-28 11:32:50 4668 [Note] InnoDB: Highest supported file format is Barracuda.
2013-07-28 11:32:50 4668 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2884023 in the ib_logfiles!
2013-07-28 11:32:50 4668 [Note] InnoDB: Database was not shutdown normally!
2013-07-28 11:32:50 4668 [Note] InnoDB: Starting crash recovery.
2013-07-28 11:32:50 4668 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-07-28 11:32:50 4668 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace wordpress/wp_terms which uses space ID: 3 at filepath: .\wordpress\wp_terms.ibd
2013-07-28 11:32:50 7252 [Note] Plugin 'FEDERATED' is disabled.
2013-07-28 11:32:50 9d4 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2013-07-28 11:32:50 7252 [Note] InnoDB: The InnoDB memory heap is disabled
2013-07-28 11:32:50 7252 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-07-28 11:32:50 7252 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-07-28 11:32:50 7252 [Note] InnoDB: Not using CPU crc32 instructions
2013-07-28 11:32:50 7252 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-07-28 11:32:50 7252 [Note] InnoDB: Completed initialization of buffer pool
2013-07-28 11:32:50 7252 [Note] InnoDB: Highest supported file format is Barracuda.
2013-07-28 11:32:50 7252 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2884023 in the ib_logfiles!
2013-07-28 11:32:50 7252 [Note] InnoDB: Database was not shutdown normally!
2013-07-28 11:32:50 7252 [Note] InnoDB: Starting crash recovery.
2013-07-28 11:32:50 7252 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-07-28 11:32:50 7252 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace wordpress/wp_terms which uses space ID: 3 at filepath: .\wordpress\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\wordpress\wp_terms.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.
2013-07-28 11:32:51 6280 [Note] Plugin 'FEDERATED' is disabled.
2013-07-28 11:32:51 1cc0 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2013-07-28 11:32:51 6280 [Note] InnoDB: The InnoDB memory heap is disabled
2013-07-28 11:32:51 6280 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-07-28 11:32:51 6280 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-07-28 11:32:51 6280 [Note] InnoDB: Not using CPU crc32 instructions
2013-07-28 11:32:51 6280 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-07-28 11:32:51 6280 [Note] InnoDB: Completed initialization of buffer pool
2013-07-28 11:32:51 6280 [Note] InnoDB: Highest supported file format is Barracuda.
2013-07-28 11:32:51 6280 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2884023 in the ib_logfiles!
2013-07-28 11:32:51 6280 [Note] InnoDB: Database was not shutdown normally!
2013-07-28 11:32:51 6280 [Note] InnoDB: Starting crash recovery.
2013-07-28 11:32:51 6280 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-07-28 11:32:51 6280 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace wordpress/wp_terms which uses space ID: 3 at filepath: .\wordpress\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\wordpress\wp_terms.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.
2013-07-28 11:32:52 7616 [Note] Plugin 'FEDERATED' is disabled.
2013-07-28 11:32:52 180c InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2013-07-28 11:32:52 7616 [Note] InnoDB: The InnoDB memory heap is disabled
2013-07-28 11:32:52 7616 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-07-28 11:32:52 7616 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-07-28 11:32:52 7616 [Note] InnoDB: Not using CPU crc32 instructions
2013-07-28 11:32:52 7616 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-07-28 11:32:52 7616 [Note] InnoDB: Completed initialization of buffer pool
2013-07-28 11:32:52 7616 [Note] InnoDB: Highest supported file format is Barracuda.
2013-07-28 11:32:52 7616 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2884023 in the ib_logfiles!
2013-07-28 11:32:52 7616 [Note] InnoDB: Database was not shutdown normally!
2013-07-28 11:32:52 7616 [Note] InnoDB: Starting crash recovery.
2013-07-28 11:32:52 7616 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-07-28 11:32:52 7616 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace wordpress/wp_terms which uses space ID: 3 at filepath: .\wordpress\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\wordpress\wp_terms.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.
2013-07-28 11:32:52 7848 [Note] Plugin 'FEDERATED' is disabled.
2013-07-28 11:32:52 19b8 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2013-07-28 11:32:52 7848 [Note] InnoDB: The InnoDB memory heap is disabled
2013-07-28 11:32:52 7848 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-07-28 11:32:52 7848 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-07-28 11:32:52 7848 [Note] InnoDB: Not using CPU crc32 instructions
2013-07-28 11:32:52 7848 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-07-28 11:32:52 7848 [Note] InnoDB: Completed initialization of buffer pool
2013-07-28 11:32:52 7848 [Note] InnoDB: Highest supported file format is Barracuda.
2013-07-28 11:32:52 7848 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2884023 in the ib_logfiles!
2013-07-28 11:32:52 7848 [Note] InnoDB: Database was not shutdown normally!
2013-07-28 11:32:52 7848 [Note] InnoDB: Starting crash recovery.
2013-07-28 11:32:52 7848 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-07-28 11:32:52 7848 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace wordpress/wp_terms which uses space ID: 3 at filepath: .\wordpress\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\wordpress\wp_terms.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.
2013-07-28 11:32:52 6364 [Note] Plugin 'FEDERATED' is disabled.
2013-07-28 11:32:52 17cc InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2013-07-28 11:32:52 6364 [Note] InnoDB: The InnoDB memory heap is disabled
2013-07-28 11:32:52 6364 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-07-28 11:32:52 6364 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-07-28 11:32:52 6364 [Note] InnoDB: Not using CPU crc32 instructions
2013-07-28 11:32:52 6364 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-07-28 11:32:52 6364 [Note] InnoDB: Completed initialization of buffer pool
2013-07-28 11:32:52 6364 [Note] InnoDB: Highest supported file format is Barracuda.
2013-07-28 11:32:52 6364 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2884023 in the ib_logfiles!
2013-07-28 11:32:52 6364 [Note] InnoDB: Database was not shutdown normally!
2013-07-28 11:32:52 6364 [Note] InnoDB: Starting crash recovery.
2013-07-28 11:32:52 6364 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-07-28 11:32:52 6364 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace wordpress/wp_terms which uses space ID: 3 at filepath: .\wordpress\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\wordpress\wp_terms.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.
2013-07-28 11:32:54 7600 [Note] Plugin 'FEDERATED' is disabled.
2013-07-28 11:32:54 5b4 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2013-07-28 11:32:54 7600 [Note] InnoDB: The InnoDB memory heap is disabled
2013-07-28 11:32:54 7600 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-07-28 11:32:54 7600 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-07-28 11:32:54 7600 [Note] InnoDB: Not using CPU crc32 instructions
2013-07-28 11:32:54 7600 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-07-28 11:32:54 7600 [Note] InnoDB: Completed initialization of buffer pool
2013-07-28 11:32:54 7600 [Note] InnoDB: Highest supported file format is Barracuda.
2013-07-28 11:32:54 7600 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2884023 in the ib_logfiles!
2013-07-28 11:32:54 7600 [Note] InnoDB: Database was not shutdown normally!
2013-07-28 11:32:54 7600 [Note] InnoDB: Starting crash recovery.
2013-07-28 11:32:54 7600 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-07-28 11:32:54 7600 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace wordpress/wp_terms which uses space ID: 3 at filepath: .\wordpress\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\wordpress\wp_terms.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.
2013-07-28 11:32:55 7052 [Note] Plugin 'FEDERATED' is disabled.
2013-07-28 11:32:55 d30 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2013-07-28 11:32:55 7052 [Note] InnoDB: The InnoDB memory heap is disabled
2013-07-28 11:32:55 7052 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-07-28 11:32:55 7052 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-07-28 11:32:55 7052 [Note] InnoDB: Not using CPU crc32 instructions
2013-07-28 11:32:55 7052 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-07-28 11:32:55 7052 [Note] InnoDB: Completed initialization of buffer pool
2013-07-28 11:32:55 7052 [Note] InnoDB: Highest supported file format is Barracuda.
2013-07-28 11:32:55 7052 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2884023 in the ib_logfiles!
2013-07-28 11:32:55 7052 [Note] InnoDB: Database was not shutdown normally!
2013-07-28 11:32:55 7052 [Note] InnoDB: Starting crash recovery.
2013-07-28 11:32:55 7052 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-07-28 11:32:55 7052 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace wordpress/wp_terms which uses space ID: 3 at filepath: .\wordpress\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\wordpress\wp_terms.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.
2013-07-28 11:32:56 7428 [Note] Plugin 'FEDERATED' is disabled.
2013-07-28 11:32:56 1c3c InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2013-07-28 11:32:56 7428 [Note] InnoDB: The InnoDB memory heap is disabled
2013-07-28 11:32:56 7428 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-07-28 11:32:56 7428 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-07-28 11:32:56 7428 [Note] InnoDB: Not using CPU crc32 instructions
2013-07-28 11:32:56 7428 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-07-28 11:32:56 7428 [Note] InnoDB: Completed initialization of buffer pool
2013-07-28 11:32:56 7428 [Note] InnoDB: Highest supported file format is Barracuda.
2013-07-28 11:32:56 7428 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2884023 in the ib_logfiles!
2013-07-28 11:32:56 7428 [Note] InnoDB: Database was not shutdown normally!
2013-07-28 11:32:56 7428 [Note] InnoDB: Starting crash recovery.
2013-07-28 11:32:56 7428 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-07-28 11:32:56 7428 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace wordpress/wp_terms which uses space ID: 3 at filepath: .\wordpress\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\wordpress\wp_terms.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.
2013-07-28 11:32:57 6020 [Note] Plugin 'FEDERATED' is disabled.
2013-07-28 11:32:57 19c0 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2013-07-28 11:32:57 6020 [Note] InnoDB: The InnoDB memory heap is disabled
2013-07-28 11:32:57 6020 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-07-28 11:32:57 6020 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-07-28 11:32:57 6020 [Note] InnoDB: Not using CPU crc32 instructions
2013-07-28 11:32:57 6020 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-07-28 11:32:57 6020 [Note] InnoDB: Completed initialization of buffer pool
2013-07-28 11:32:57 6020 [Note] InnoDB: Highest supported file format is Barracuda.
2013-07-28 11:32:57 6020 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2884023 in the ib_logfiles!
2013-07-28 11:32:57 6020 [Note] InnoDB: Database was not shutdown normally!
2013-07-28 11:32:57 6020 [Note] InnoDB: Starting crash recovery.
2013-07-28 11:32:57 6020 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-07-28 11:32:58 6020 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace wordpress/wp_terms which uses space ID: 3 at filepath: .\wordpress\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\wordpress\wp_terms.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.
It's a big log, I cut some of the parts that repeated in the log, so that the message can be posted here. I hope this is an easy fix and I am very looking forward to your support.
Thanks,
Matas