Error: MySQL shutdown unexpectedly

Problems with the Windows version of XAMPP, questions, comments, and anything related.

Error: MySQL shutdown unexpectedly

Postby chapht » 25. September 2013 13:44

XAMPP Windows 1.8.3 and MS Windows 7 Ultimate Edition

Error Report Directly from XAMPP Control Panel V3.2.1
9:40:24 PM [main] Initializing Control Panel
9:40:24 PM [main] Windows Version: Windows 7 Ultimate SP1 32-bit
9:40:24 PM [main] XAMPP Version: 1.8.3
9:40:24 PM [main] Control Panel Version: 3.2.1 [ Compiled: May 7th 2013 ]
9:40:24 PM [main] Running with Administrator rights - good!
9:40:24 PM [main] XAMPP Installation Directory: "c:\xampp\"
9:40:24 PM [main] Checking for prerequisites
9:40:24 PM [main] All prerequisites found
9:40:24 PM [main] Initializing Modules
9:40:24 PM [main] Starting Check-Timer
9:40:24 PM [main] Control Panel Ready
9:40:30 PM [Apache] Attempting to start Apache app...
9:40:30 PM [Apache] Status change detected: running
9:40:42 PM [mysql] Attempting to start MySQL app...
9:40:42 PM [mysql] Status change detected: running
9:40:49 PM [mysql] Status change detected: stopped
9:40:49 PM [mysql] Error: MySQL shutdown unexpectedly.
9:40:49 PM [mysql] This may be due to a blocked port, missing dependencies,
9:40:49 PM [mysql] improper privileges, a crash, or a shutdown by another method.
9:40:49 PM [mysql] Press the Logs button to view error logs and check
9:40:49 PM [mysql] the Windows Event Viewer for more clues
9:40:49 PM [mysql] If you need more help, copy and post this
9:40:49 PM [mysql] entire log window on the forums
9:41:18 PM [mysql] Attempting to start MySQL app...
9:41:18 PM [mysql] Status change detected: running
9:41:18 PM [mysql] Status change detected: stopped

Error Report from the Windows Logs > Application
Log Name: Application
Source: MySQL
Date: 25/09/2013 9:41:24 PM
Event ID: 100
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: HCT-Dell-M1330
Description:
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 tee/wp_terms which uses space ID: 3 at filepath: .\tee\wp_terms.ibd

For more information, see Help and Support Center at http://www.mysql.com.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MySQL" />
<EventID Qualifiers="49152">100</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-09-25T11:41:24.000000000Z" />
<EventRecordID>33230</EventRecordID>
<Channel>Application</Channel>
<Computer>HCT-Dell-M1330</Computer>
<Security />
</System>
<EventData>
<Data>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 tee/wp_terms which uses space ID: 3 at filepath: .\tee\wp_terms.ibd

</Data>
</EventData>
</Event>

Error Report from MySQL_Error.LOG of XAMPP Control Panel V3.2.1
2013-09-24 12:00:13 4640 [Note] Plugin 'FEDERATED' is disabled.
2013-09-24 12:00:14 518 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-09-24 12:00:14 4640 [Note] InnoDB: The InnoDB memory heap is disabled
2013-09-24 12:00:14 4640 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-09-24 12:00:14 4640 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-09-24 12:00:14 4640 [Note] InnoDB: Not using CPU crc32 instructions
2013-09-24 12:00:14 4640 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-09-24 12:00:14 4640 [Note] InnoDB: Completed initialization of buffer pool
2013-09-24 12:00:14 4640 [Note] InnoDB: The first specified data file C:\xampp\mysql\data\ibdata1 did not exist: a new database to be created!
2013-09-24 12:00:14 4640 [Note] InnoDB: Setting file C:\xampp\mysql\data\ibdata1 size to 10 MB
2013-09-24 12:00:14 4640 [Note] InnoDB: Database physically writes the file full: wait...
2013-09-24 12:00:16 4640 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile101 size to 5 MB
2013-09-24 12:00:17 4640 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile1 size to 5 MB
2013-09-24 12:00:20 4640 [Note] InnoDB: Renaming log file C:\xampp\mysql\data\ib_logfile101 to C:\xampp\mysql\data\ib_logfile0
2013-09-24 12:00:21 4640 [Warning] InnoDB: New log files created, LSN=45781
2013-09-24 12:00:21 4640 [Note] InnoDB: Doublewrite buffer not found: creating new
2013-09-24 12:00:26 4640 [Note] InnoDB: Doublewrite buffer created
2013-09-24 12:00:44 4640 [Note] InnoDB: 128 rollback segment(s) are active.
2013-09-24 12:00:44 4640 [Warning] InnoDB: Creating foreign key constraint system tables.
2013-09-24 12:00:45 4640 [Note] InnoDB: Foreign key constraint system tables created
2013-09-24 12:00:45 4640 [Note] InnoDB: Creating tablespace and datafile system tables.
2013-09-24 12:00:45 4640 [Note] InnoDB: Tablespace and datafile system tables created.
2013-09-24 12:00:45 4640 [Note] InnoDB: Waiting for purge to start
2013-09-24 12:00:45 4640 [Note] InnoDB: 5.6.11 started; log sequence number 0
2013-09-24 12:00:46 4640 [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: 204802ab-24bd-11e3-b26c-0015c57ef999.
2013-09-24 12:00:46 4640 [Note] Server hostname (bind-address): '*'; port: 3306
2013-09-24 12:00:46 4640 [Note] IPv6 is available.
2013-09-24 12:00:46 4640 [Note] - '::' resolves to '::';
2013-09-24 12:00:46 4640 [Note] Server socket created on IP: '::'.
2013-09-24 12:00:57 4640 [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-09-24 12:00:57 4640 [Warning] Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.
2013-09-24 12:00:57 4640 [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-09-24 12:00:57 4640 [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-09-24 12:00:57 4640 [Warning] Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.
2013-09-24 12:01:08 4640 [Note] Event Scheduler: Loaded 0 events
2013-09-24 12:01:08 4640 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.11' socket: '' port: 3306 MySQL Community Server (GPL)
2013-09-24 12:27:24 4640 [Warning] InnoDB: Cannot open table mysql/innodb_index_stats 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-09-24 12:27:24 4640 [Warning] InnoDB: Cannot open table mysql/innodb_table_stats 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-09-24 12:27:24 4640 [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-09-24 12:27:24 4640 [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-09-24 12:27:24 4640 [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-09-24 12:27:25 4640 [Warning] InnoDB: Cannot open table mysql/innodb_index_stats 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-09-24 12:27:25 4640 [Warning] InnoDB: Cannot open table mysql/innodb_table_stats 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-09-24 12:27:25 4640 [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-09-24 12:27:25 4640 [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-09-24 12:27:25 4640 [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-09-24 12:27:25 4640 [Warning] InnoDB: Cannot open table mysql/innodb_index_stats 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-09-24 12:27:25 4640 [Warning] InnoDB: Cannot open table mysql/innodb_table_stats 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-09-24 12:27:25 4640 [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-09-24 12:27:25 4640 [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-09-24 12:27:25 4640 [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-09-24 12:27:25 4640 [Warning] InnoDB: Cannot open table mysql/innodb_index_stats 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-09-24 12:27:25 4640 [Warning] InnoDB: Cannot open table mysql/innodb_table_stats 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-09-24 12:27:25 4640 [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-09-24 12:27:25 4640 [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-09-24 12:27:25 4640 [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-09-24 12:30:13 23f0 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-09-24 12:30:13 23f0 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-09-24 12:30:13 23f0 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-09-24 12:30:13 23f0 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-09-24 12:30:13 23f0 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-09-24 12:30:13 23f0 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-09-24 12:30:13 23f0 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-09-24 12:30:13 23f0 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-09-24 12:30:13 23f0 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-09-24 12:30:13 23f0 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-09-24 12:30:13 23f0 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-09-24 12:30:13 23f0 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-09-24 12:30:13 23f0 InnoDB: Error: Fetch of persistent statistics requested for table "tee"."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-09-24 12:30:14 23f0 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-09-24 12:30:14 23f0 InnoDB: Error: Fetch of persistent statistics requested for table "tee"."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-09-24 12:30:14 23f0 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-09-24 12:30:14 23f0 InnoDB: Error: Fetch of persistent statistics requested for table "tee"."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-09-24 12:30:14 23f0 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-09-24 12:30:14 23f0 InnoDB: Error: Fetch of persistent statistics requested for table "tee"."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-09-24 12:30:14 23f0 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-09-24 12:30:14 23f0 InnoDB: Error: Fetch of persistent statistics requested for table "tee"."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-09-24 12:30:14 23f0 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-09-24 12:30:14 23f0 InnoDB: Error: Fetch of persistent statistics requested for table "tee"."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-09-24 12:30:14 23f0 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-09-24 12:30:14 23f0 InnoDB: Error: Fetch of persistent statistics requested for table "tee"."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-09-24 12:30:14 23f0 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-09-24 12:30:14 23f0 InnoDB: Error: Fetch of persistent statistics requested for table "tee"."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-09-24 12:30:14 23f0 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-09-24 12:30:14 23f0 InnoDB: Error: Fetch of persistent statistics requested for table "tee"."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-09-24 12:30:24 183c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-09-24 12:30:24 183c InnoDB: Recalculation of persistent statistics requested for table "tee"."wp_options" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-09-24 12:30:34 183c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-09-24 12:30:34 183c InnoDB: Recalculation of persistent statistics requested for table "tee"."wp_posts" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-09-24 12:30:38 183c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-09-24 12:30:38 183c InnoDB: Recalculation of persistent statistics requested for table "tee"."wp_usermeta" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-09-24 12:30:48 183c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-09-24 12:30:48 183c InnoDB: Recalculation of persistent statistics requested for table "tee"."wp_options" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-09-24 16:18:39 6288 [Note] Plugin 'FEDERATED' is disabled.
2013-09-24 16:18:39 15dc 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-09-24 16:18:40 6288 [Note] InnoDB: The InnoDB memory heap is disabled
2013-09-24 16:18:40 6288 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-09-24 16:18:40 6288 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-09-24 16:18:40 6288 [Note] InnoDB: Not using CPU crc32 instructions
2013-09-24 16:18:40 6288 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-09-24 16:18:40 6288 [Note] InnoDB: Completed initialization of buffer pool
2013-09-24 16:18:40 6288 [Note] InnoDB: Highest supported file format is Barracuda.
2013-09-24 16:18:40 6288 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2708253 in the ib_logfiles!
2013-09-24 16:18:40 6288 [Note] InnoDB: Database was not shutdown normally!
2013-09-24 16:18:40 6288 [Note] InnoDB: Starting crash recovery.
2013-09-24 16:18:40 6288 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-09-24 16:18:40 6288 [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 tee/wp_terms which uses space ID: 3 at filepath: .\tee\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\tee\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-09-25 16:29:48 9236 [Note] Plugin 'FEDERATED' is disabled.
2013-09-25 16:29:48 2418 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-09-25 16:29:48 9236 [Note] InnoDB: The InnoDB memory heap is disabled
2013-09-25 16:29:48 9236 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-09-25 16:29:48 9236 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-09-25 16:29:49 9236 [Note] InnoDB: Not using CPU crc32 instructions
2013-09-25 16:29:49 9236 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-09-25 16:29:49 9236 [Note] InnoDB: Completed initialization of buffer pool
2013-09-25 16:29:49 9236 [Note] InnoDB: Highest supported file format is Barracuda.
2013-09-25 16:29:49 9236 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2708253 in the ib_logfiles!
2013-09-25 16:29:49 9236 [Note] InnoDB: Database was not shutdown normally!
2013-09-25 16:29:49 9236 [Note] InnoDB: Starting crash recovery.
2013-09-25 16:29:49 9236 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-09-25 16:29:50 9236 [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 tee/wp_terms which uses space ID: 3 at filepath: .\tee\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\tee\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-09-25 16:32:50 7776 [Note] Plugin 'FEDERATED' is disabled.
2013-09-25 16:32:50 2550 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-09-25 16:32:50 7776 [Note] InnoDB: The InnoDB memory heap is disabled
2013-09-25 16:32:50 7776 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-09-25 16:32:50 7776 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-09-25 16:32:50 7776 [Note] InnoDB: Not using CPU crc32 instructions
2013-09-25 16:32:50 7776 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-09-25 16:32:50 7776 [Note] InnoDB: Completed initialization of buffer pool
2013-09-25 16:32:50 7776 [Note] InnoDB: Highest supported file format is Barracuda.
2013-09-25 16:32:50 7776 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2708253 in the ib_logfiles!
2013-09-25 16:32:50 7776 [Note] InnoDB: Database was not shutdown normally!
2013-09-25 16:32:50 7776 [Note] InnoDB: Starting crash recovery.
2013-09-25 16:32:50 7776 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-09-25 16:32:50 7776 [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 tee/wp_terms which uses space ID: 3 at filepath: .\tee\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\tee\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-09-25 16:34:50 9548 [Note] Plugin 'FEDERATED' is disabled.
2013-09-25 16:34:50 20f8 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-09-25 16:34:50 9548 [Note] InnoDB: The InnoDB memory heap is disabled
2013-09-25 16:34:50 9548 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-09-25 16:34:50 9548 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-09-25 16:34:50 9548 [Note] InnoDB: Not using CPU crc32 instructions
2013-09-25 16:34:50 9548 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-09-25 16:34:50 9548 [Note] InnoDB: Completed initialization of buffer pool
2013-09-25 16:34:50 9548 [Note] InnoDB: Highest supported file format is Barracuda.
2013-09-25 16:34:50 9548 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2708253 in the ib_logfiles!
2013-09-25 16:34:50 9548 [Note] InnoDB: Database was not shutdown normally!
2013-09-25 16:34:50 9548 [Note] InnoDB: Starting crash recovery.
2013-09-25 16:34:50 9548 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-09-25 16:34:50 9548 [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 tee/wp_terms which uses space ID: 3 at filepath: .\tee\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\tee\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-09-25 16:36:10 9360 [Note] Plugin 'FEDERATED' is disabled.
2013-09-25 16:36:10 26c0 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-09-25 16:36:10 9360 [Note] InnoDB: The InnoDB memory heap is disabled
2013-09-25 16:36:10 9360 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-09-25 16:36:10 9360 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-09-25 16:36:10 9360 [Note] InnoDB: Not using CPU crc32 instructions
2013-09-25 16:36:10 9360 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-09-25 16:36:10 9360 [Note] InnoDB: Completed initialization of buffer pool
2013-09-25 16:36:10 9360 [Note] InnoDB: Highest supported file format is Barracuda.
2013-09-25 16:36:10 9360 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2708253 in the ib_logfiles!
2013-09-25 16:36:10 9360 [Note] InnoDB: Database was not shutdown normally!
2013-09-25 16:36:10 9360 [Note] InnoDB: Starting crash recovery.
2013-09-25 16:36:10 9360 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-09-25 16:36:10 9360 [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 tee/wp_terms which uses space ID: 3 at filepath: .\tee\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\tee\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-09-25 16:36:15 9628 [Note] Plugin 'FEDERATED' is disabled.
2013-09-25 16:36:15 27b0 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-09-25 16:36:15 9628 [Note] InnoDB: The InnoDB memory heap is disabled
2013-09-25 16:36:15 9628 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-09-25 16:36:15 9628 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-09-25 16:36:15 9628 [Note] InnoDB: Not using CPU crc32 instructions
2013-09-25 16:36:15 9628 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-09-25 16:36:15 9628 [Note] InnoDB: Completed initialization of buffer pool
2013-09-25 16:36:15 9628 [Note] InnoDB: Highest supported file format is Barracuda.
2013-09-25 16:36:15 9628 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2708253 in the ib_logfiles!
2013-09-25 16:36:15 9628 [Note] InnoDB: Database was not shutdown normally!
2013-09-25 16:36:15 9628 [Note] InnoDB: Starting crash recovery.
2013-09-25 16:36:15 9628 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-09-25 16:36:15 9628 [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 tee/wp_terms which uses space ID: 3 at filepath: .\tee\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\tee\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-09-25 16:36:39 9740 [Note] Plugin 'FEDERATED' is disabled.
2013-09-25 16:36:39 2328 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-09-25 16:36:39 9740 [Note] InnoDB: The InnoDB memory heap is disabled
2013-09-25 16:36:39 9740 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-09-25 16:36:39 9740 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-09-25 16:36:39 9740 [Note] InnoDB: Not using CPU crc32 instructions
2013-09-25 16:36:39 9740 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-09-25 16:36:39 9740 [Note] InnoDB: Completed initialization of buffer pool
2013-09-25 16:36:39 9740 [Note] InnoDB: Highest supported file format is Barracuda.
2013-09-25 16:36:39 9740 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2708253 in the ib_logfiles!
2013-09-25 16:36:39 9740 [Note] InnoDB: Database was not shutdown normally!
2013-09-25 16:36:39 9740 [Note] InnoDB: Starting crash recovery.
2013-09-25 16:36:39 9740 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-09-25 16:36:39 9740 [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 tee/wp_terms which uses space ID: 3 at filepath: .\tee\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\tee\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-09-25 16:47:23 8428 [Note] Plugin 'FEDERATED' is disabled.
2013-09-25 16:47:23 25c0 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-09-25 16:47:23 8428 [Note] InnoDB: The InnoDB memory heap is disabled
2013-09-25 16:47:23 8428 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-09-25 16:47:23 8428 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-09-25 16:47:23 8428 [Note] InnoDB: Not using CPU crc32 instructions
2013-09-25 16:47:23 8428 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-09-25 16:47:23 8428 [Note] InnoDB: Completed initialization of buffer pool
2013-09-25 16:47:23 8428 [Note] InnoDB: Highest supported file format is Barracuda.
2013-09-25 16:47:23 8428 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2708253 in the ib_logfiles!
2013-09-25 16:47:23 8428 [Note] InnoDB: Database was not shutdown normally!
2013-09-25 16:47:23 8428 [Note] InnoDB: Starting crash recovery.
2013-09-25 16:47:23 8428 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-09-25 16:47:23 8428 [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 tee/wp_terms which uses space ID: 3 at filepath: .\tee\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\tee\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-09-25 16:48:27 7432 [Note] Plugin 'FEDERATED' is disabled.
2013-09-25 16:48:27 1a78 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-09-25 16:48:27 7432 [Note] InnoDB: The InnoDB memory heap is disabled
2013-09-25 16:48:27 7432 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-09-25 16:48:27 7432 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-09-25 16:48:27 7432 [Note] InnoDB: Not using CPU crc32 instructions
2013-09-25 16:48:27 7432 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-09-25 16:48:27 7432 [Note] InnoDB: Completed initialization of buffer pool
2013-09-25 16:48:27 7432 [Note] InnoDB: Highest supported file format is Barracuda.
2013-09-25 16:48:28 7432 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2708253 in the ib_logfiles!
2013-09-25 16:48:28 7432 [Note] InnoDB: Database was not shutdown normally!
2013-09-25 16:48:28 7432 [Note] InnoDB: Starting crash recovery.
2013-09-25 16:48:28 7432 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-09-25 16:48:28 7432 [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 tee/wp_terms which uses space ID: 3 at filepath: .\tee\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\tee\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-09-25 16:48:43 8396 [Note] Plugin 'FEDERATED' is disabled.
2013-09-25 16:48:43 2368 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-09-25 16:48:43 8396 [Note] InnoDB: The InnoDB memory heap is disabled
2013-09-25 16:48:43 8396 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-09-25 16:48:43 8396 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-09-25 16:48:43 8396 [Note] InnoDB: Not using CPU crc32 instructions
2013-09-25 16:48:43 8396 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-09-25 16:48:43 8396 [Note] InnoDB: Completed initialization of buffer pool
2013-09-25 16:48:43 8396 [Note] InnoDB: Highest supported file format is Barracuda.
2013-09-25 16:48:43 8396 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2708253 in the ib_logfiles!
2013-09-25 16:48:43 8396 [Note] InnoDB: Database was not shutdown normally!
2013-09-25 16:48:43 8396 [Note] InnoDB: Starting crash recovery.
2013-09-25 16:48:43 8396 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-09-25 16:48:43 8396 [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 tee/wp_terms which uses space ID: 3 at filepath: .\tee\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\tee\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-09-25 16:49:18 8452 [Note] Plugin 'FEDERATED' is disabled.
2013-09-25 16:49:18 232c 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-09-25 16:49:18 8452 [Note] InnoDB: The InnoDB memory heap is disabled
2013-09-25 16:49:18 8452 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-09-25 16:49:18 8452 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-09-25 16:49:18 8452 [Note] InnoDB: Not using CPU crc32 instructions
2013-09-25 16:49:18 8452 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-09-25 16:49:18 8452 [Note] InnoDB: Completed initialization of buffer pool
2013-09-25 16:49:18 8452 [Note] InnoDB: Highest supported file format is Barracuda.
2013-09-25 16:49:18 8452 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2708253 in the ib_logfiles!
2013-09-25 16:49:18 8452 [Note] InnoDB: Database was not shutdown normally!
2013-09-25 16:49:18 8452 [Note] InnoDB: Starting crash recovery.
2013-09-25 16:49:18 8452 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-09-25 16:49:18 8452 [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 tee/wp_terms which uses space ID: 3 at filepath: .\tee\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\tee\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-09-25 16:49:22 10020 [Note] Plugin 'FEDERATED' is disabled.
2013-09-25 16:49:22 2168 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-09-25 16:49:22 10020 [Note] InnoDB: The InnoDB memory heap is disabled
2013-09-25 16:49:22 10020 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-09-25 16:49:22 10020 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-09-25 16:49:22 10020 [Note] InnoDB: Not using CPU crc32 instructions
2013-09-25 16:49:22 10020 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-09-25 16:49:22 10020 [Note] InnoDB: Completed initialization of buffer pool
2013-09-25 16:49:22 10020 [Note] InnoDB: Highest supported file format is Barracuda.
2013-09-25 16:49:22 10020 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2708253 in the ib_logfiles!
2013-09-25 16:49:22 10020 [Note] InnoDB: Database was not shutdown normally!
2013-09-25 16:49:22 10020 [Note] InnoDB: Starting crash recovery.
2013-09-25 16:49:22 10020 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-09-25 16:49:22 10020 [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 tee/wp_terms which uses space ID: 3 at filepath: .\tee\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\tee\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-09-25 16:49:29 6992 [Note] Plugin 'FEDERATED' is disabled.
2013-09-25 16:49:29 1e70 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-09-25 16:49:29 6992 [Note] InnoDB: The InnoDB memory heap is disabled
2013-09-25 16:49:29 6992 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-09-25 16:49:29 6992 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-09-25 16:49:29 6992 [Note] InnoDB: Not using CPU crc32 instructions
2013-09-25 16:49:29 6992 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-09-25 16:49:29 6992 [Note] InnoDB: Completed initialization of buffer pool
2013-09-25 16:49:29 6992 [Note] InnoDB: Highest supported file format is Barracuda.
2013-09-25 16:49:29 6992 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2708253 in the ib_logfiles!
2013-09-25 16:49:29 6992 [Note] InnoDB: Database was not shutdown normally!
2013-09-25 16:49:29 6992 [Note] InnoDB: Starting crash recovery.
2013-09-25 16:49:29 6992 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-09-25 16:49:29 6992 [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 tee/wp_terms which uses space ID: 3 at filepath: .\tee\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\tee\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-09-25 16:50:42 9872 [Note] Plugin 'FEDERATED' is disabled.
2013-09-25 16:50:42 21a4 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-09-25 16:50:42 9872 [Note] InnoDB: The InnoDB memory heap is disabled
2013-09-25 16:50:42 9872 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-09-25 16:50:42 9872 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-09-25 16:50:42 9872 [Note] InnoDB: Not using CPU crc32 instructions
2013-09-25 16:50:42 9872 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-09-25 16:50:42 9872 [Note] InnoDB: Completed initialization of buffer pool
2013-09-25 16:50:42 9872 [Note] InnoDB: Highest supported file format is Barracuda.
2013-09-25 16:50:42 9872 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2708253 in the ib_logfiles!
2013-09-25 16:50:42 9872 [Note] InnoDB: Database was not shutdown normally!
2013-09-25 16:50:42 9872 [Note] InnoDB: Starting crash recovery.
2013-09-25 16:50:42 9872 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-09-25 16:50:42 9872 [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 tee/wp_terms which uses space ID: 3 at filepath: .\tee\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\tee\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-09-25 16:51:17 10028 [Note] Plugin 'FEDERATED' is disabled.
2013-09-25 16:51:17 21a8 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-09-25 16:51:17 10028 [Note] InnoDB: The InnoDB memory heap is disabled
2013-09-25 16:51:17 10028 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-09-25 16:51:17 10028 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-09-25 16:51:17 10028 [Note] InnoDB: Not using CPU crc32 instructions
2013-09-25 16:51:17 10028 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-09-25 16:51:17 10028 [Note] InnoDB: Completed initialization of buffer pool
2013-09-25 16:51:17 10028 [Note] InnoDB: Highest supported file format is Barracuda.
2013-09-25 16:51:17 10028 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2708253 in the ib_logfiles!
2013-09-25 16:51:17 10028 [Note] InnoDB: Database was not shutdown normally!
2013-09-25 16:51:17 10028 [Note] InnoDB: Starting crash recovery.
2013-09-25 16:51:17 10028 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-09-25 16:51:17 10028 [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 tee/wp_terms which uses space ID: 3 at filepath: .\tee\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\tee\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-09-25 16:51:21 9800 [Note] Plugin 'FEDERATED' is disabled.
2013-09-25 16:51:21 2208 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-09-25 16:51:21 9800 [Note] InnoDB: The InnoDB memory heap is disabled
2013-09-25 16:51:21 9800 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-09-25 16:51:21 9800 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-09-25 16:51:21 9800 [Note] InnoDB: Not using CPU crc32 instructions
2013-09-25 16:51:21 9800 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-09-25 16:51:21 9800 [Note] InnoDB: Completed initialization of buffer pool
2013-09-25 16:51:21 9800 [Note] InnoDB: Highest supported file format is Barracuda.
2013-09-25 16:51:21 9800 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2708253 in the ib_logfiles!
2013-09-25 16:51:21 9800 [Note] InnoDB: Database was not shutdown normally!
2013-09-25 16:51:21 9800 [Note] InnoDB: Starting crash recovery.
2013-09-25 16:51:21 9800 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-09-25 16:51:21 9800 [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 tee/wp_terms which uses space ID: 3 at filepath: .\tee\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\tee\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-09-25 16:53:17 9056 [Note] Plugin 'FEDERATED' is disabled.
2013-09-25 16:53:17 2494 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-09-25 16:53:17 9056 [Note] InnoDB: The InnoDB memory heap is disabled
2013-09-25 16:53:17 9056 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-09-25 16:53:17 9056 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-09-25 16:53:17 9056 [Note] InnoDB: Not using CPU crc32 instructions
2013-09-25 16:53:17 9056 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-09-25 16:53:17 9056 [Note] InnoDB: Completed initialization of buffer pool
2013-09-25 16:53:18 9056 [Note] InnoDB: Highest supported file format is Barracuda.
2013-09-25 16:53:18 9056 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2708253 in the ib_logfiles!
2013-09-25 16:53:18 9056 [Note] InnoDB: Database was not shutdown normally!
2013-09-25 16:53:18 9056 [Note] InnoDB: Starting crash recovery.
2013-09-25 16:53:18 9056 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-09-25 16:53:18 9056 [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 tee/wp_terms which uses space ID: 3 at filepath: .\tee\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\tee\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.
chapht
 
Posts: 3
Joined: 25. September 2013 13:03
XAMPP Version: 5.5.19
Operating System: MS Windows 7 Ultimate Edition

Re: Error: MySQL shutdown unexpectedly

Postby chapht » 02. October 2013 07:01

For XAMPP 1.8.3 with XAMPP Control Panel V3.2.1. It is a known bug with feasible "Solution and Workaround" is given by deleting the file (ibdata1) at the directory folder C:\xampp\mysql\data\ before starting or activating to run MySQL Server each time....

Thanks for those viewers even though without offering any suggestions!!!!!
chapht
 
Posts: 3
Joined: 25. September 2013 13:03
XAMPP Version: 5.5.19
Operating System: MS Windows 7 Ultimate Edition


Return to XAMPP for Windows

Who is online

Users browsing this forum: JJ_Tagy and 53 guests