MYSQL starts then immediately stops
Posted: 22. November 2013 02:00It worked before, I didn't make any changes. Apache and TomCat work.
Here is the log. Please help me.
2013-11-17 22:26:59 4844 [Note] Plugin 'FEDERATED' is disabled.
2013-11-17 22:26:59 114c 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-11-17 22:26:59 4844 [Note] InnoDB: The InnoDB memory heap is disabled
2013-11-17 22:26:59 4844 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-11-17 22:26:59 4844 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-11-17 22:26:59 4844 [Note] InnoDB: Not using CPU crc32 instructions
2013-11-17 22:26:59 4844 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-11-17 22:26:59 4844 [Note] InnoDB: Completed initialization of buffer pool
2013-11-17 22:26:59 4844 [Note] InnoDB: The first specified data file C:\xampp\mysql\data\ibdata1 did not exist: a new database to be created!
2013-11-17 22:26:59 4844 [Note] InnoDB: Setting file C:\xampp\mysql\data\ibdata1 size to 10 MB
2013-11-17 22:26:59 4844 [Note] InnoDB: Database physically writes the file full: wait...
2013-11-17 22:27:00 4844 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile101 size to 5 MB
2013-11-17 22:27:00 4844 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile1 size to 5 MB
2013-11-17 22:27:01 4844 [Note] InnoDB: Renaming log file C:\xampp\mysql\data\ib_logfile101 to C:\xampp\mysql\data\ib_logfile0
2013-11-17 22:27:01 4844 [Warning] InnoDB: New log files created, LSN=45781
2013-11-17 22:27:01 4844 [Note] InnoDB: Doublewrite buffer not found: creating new
2013-11-17 22:27:01 4844 [Note] InnoDB: Doublewrite buffer created
2013-11-17 22:27:03 4844 [Note] InnoDB: 128 rollback segment(s) are active.
2013-11-17 22:27:03 4844 [Warning] InnoDB: Creating foreign key constraint system tables.
2013-11-17 22:27:04 4844 [Note] InnoDB: Foreign key constraint system tables created
2013-11-17 22:27:04 4844 [Note] InnoDB: Creating tablespace and datafile system tables.
2013-11-17 22:27:04 4844 [Note] InnoDB: Tablespace and datafile system tables created.
2013-11-17 22:27:04 4844 [Note] InnoDB: Waiting for purge to start
2013-11-17 22:27:04 4844 [Note] InnoDB: 5.6.11 started; log sequence number 0
2013-11-17 22:27:04 4844 [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: 0f03cf4f-5012-11e3-8cfc-001e687a4c8e.
2013-11-17 22:27:04 4844 [Note] Server hostname (bind-address): '*'; port: 3306
2013-11-17 22:27:04 4844 [Note] IPv6 is available.
2013-11-17 22:27:04 4844 [Note] - '::' resolves to '::';
2013-11-17 22:27:04 4844 [Note] Server socket created on IP: '::'.
2013-11-17 22:27:07 4844 [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-11-17 22:27:07 4844 [Warning] Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.
2013-11-17 22:27:07 4844 [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-11-17 22:27:07 4844 [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-11-17 22:27:07 4844 [Warning] Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.
2013-11-17 22:27:10 4844 [Note] Event Scheduler: Loaded 0 events
2013-11-17 22:27:10 4844 [Note] C:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.11' socket: '' port: 3306 MySQL Community Server (GPL)
2013-11-17 22:37:09 4844 [Note] C:\xampp\mysql\bin\mysqld.exe: Normal shutdown
2013-11-17 22:37:09 4844 [Note] Giving 0 client threads a chance to die gracefully
2013-11-17 22:37:09 4844 [Note] Event Scheduler: Purging the queue. 0 events
2013-11-17 22:37:09 4844 [Note] Shutting down slave threads
2013-11-17 22:37:09 4844 [Note] Forcefully disconnecting 0 remaining clients
2013-11-17 22:37:09 4844 [Note] Binlog end
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'partition'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_METRICS'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_CMPMEM'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_CMP'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_LOCKS'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_TRX'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'InnoDB'
2013-11-17 22:37:09 4844 [Note] InnoDB: FTS optimize thread exiting.
2013-11-17 22:37:09 4844 [Note] InnoDB: Starting shutdown...
2013-11-17 22:37:11 4844 [Note] InnoDB: Shutdown completed; log sequence number 1600614
2013-11-17 22:37:11 4844 [Note] Shutting down plugin 'BLACKHOLE'
2013-11-17 22:37:11 4844 [Note] Shutting down plugin 'ARCHIVE'
2013-11-17 22:37:11 4844 [Note] Shutting down plugin 'MRG_MYISAM'
2013-11-17 22:37:11 4844 [Note] Shutting down plugin 'MyISAM'
2013-11-17 22:37:11 4844 [Note] Shutting down plugin 'MEMORY'
2013-11-17 22:37:11 4844 [Note] Shutting down plugin 'CSV'
2013-11-17 22:37:11 4844 [Note] Shutting down plugin 'sha256_password'
2013-11-17 22:37:11 4844 [Note] Shutting down plugin 'mysql_old_password'
2013-11-17 22:37:11 4844 [Note] Shutting down plugin 'mysql_native_password'
2013-11-17 22:37:11 4844 [Note] Shutting down plugin 'binlog'
2013-11-17 22:37:11 4844 [Note] C:\xampp\mysql\bin\mysqld.exe: Shutdown complete
2013-11-17 22:37:12 5708 [Note] Plugin 'FEDERATED' is disabled.
2013-11-17 22:37:12 16c4 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-11-17 22:37:12 5708 [Note] InnoDB: The InnoDB memory heap is disabled
2013-11-17 22:37:12 5708 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-11-17 22:37:12 5708 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-11-17 22:37:12 5708 [Note] InnoDB: Not using CPU crc32 instructions
2013-11-17 22:37:12 5708 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-11-17 22:37:12 5708 [Note] InnoDB: Completed initialization of buffer pool
2013-11-17 22:37:12 5708 [Note] InnoDB: Highest supported file format is Barracuda.
2013-11-17 22:37:13 5708 [Note] InnoDB: 128 rollback segment(s) are active.
2013-11-17 22:37:13 5708 [Note] InnoDB: Waiting for purge to start
2013-11-17 22:37:13 5708 [Note] InnoDB: 5.6.11 started; log sequence number 1600614
2013-11-17 22:37:13 5708 [Note] Server hostname (bind-address): '*'; port: 3306
2013-11-17 22:37:13 5708 [Note] IPv6 is available.
2013-11-17 22:37:13 5708 [Note] - '::' resolves to '::';
2013-11-17 22:37:13 5708 [Note] Server socket created on IP: '::'.
2013-11-17 22:37:16 5708 [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-11-17 22:37:16 5708 [Warning] Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.
2013-11-17 22:37:16 5708 [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-11-17 22:37:16 5708 [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-11-17 22:37:16 5708 [Warning] Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.
2013-11-17 22:37:16 5708 [Note] Event Scheduler: Loaded 0 events
2013-11-17 22:37:16 5708 [Note] C:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.11' socket: '' port: 3306 MySQL Community Server (GPL)
2013-11-17 23:16:56 5708 [Note] C:\xampp\mysql\bin\mysqld.exe: Normal shutdown
2013-11-17 23:16:56 5708 [Note] Giving 0 client threads a chance to die gracefully
2013-11-17 23:16:56 5708 [Note] Event Scheduler: Purging the queue. 0 events
2013-11-17 23:16:56 5708 [Note] Shutting down slave threads
2013-11-17 23:16:56 5708 [Note] Forcefully disconnecting 0 remaining clients
2013-11-17 23:16:56 5708 [Note] Binlog end
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'partition'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_METRICS'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_CMPMEM'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_CMP'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_LOCKS'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_TRX'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'InnoDB'
2013-11-17 23:16:56 5708 [Note] InnoDB: FTS optimize thread exiting.
2013-11-17 23:16:56 5708 [Note] InnoDB: Starting shutdown...
2013-11-17 23:17:12 5708 [Note] InnoDB: Shutdown completed; log sequence number 1600624
2013-11-17 23:17:12 5708 [Note] Shutting down plugin 'BLACKHOLE'
2013-11-17 23:17:12 5708 [Note] Shutting down plugin 'ARCHIVE'
2013-11-17 23:17:12 5708 [Note] Shutting down plugin 'MRG_MYISAM'
2013-11-17 23:17:12 5708 [Note] Shutting down plugin 'MyISAM'
2013-11-17 23:17:12 5708 [Note] Shutting down plugin 'MEMORY'
2013-11-17 23:17:12 5708 [Note] Shutting down plugin 'CSV'
2013-11-17 23:17:12 5708 [Note] Shutting down plugin 'sha256_password'
2013-11-17 23:17:12 5708 [Note] Shutting down plugin 'mysql_old_password'
2013-11-17 23:17:12 5708 [Note] Shutting down plugin 'mysql_native_password'
2013-11-17 23:17:12 5708 [Note] Shutting down plugin 'binlog'
2013-11-17 23:17:13 5708 [Note] C:\xampp\mysql\bin\mysqld.exe: Shutdown complete
2013-11-18 21:41:33 2016 [Note] Plugin 'FEDERATED' is disabled.
2013-11-18 21:41:33 7ec 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-11-18 21:41:33 2016 [Note] InnoDB: The InnoDB memory heap is disabled
2013-11-18 21:41:33 2016 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-11-18 21:41:33 2016 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-11-18 21:41:34 2016 [Note] InnoDB: Not using CPU crc32 instructions
2013-11-18 21:41:34 2016 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-11-18 21:41:34 2016 [Note] InnoDB: Completed initialization of buffer pool
2013-11-18 21:41:34 2016 [Note] InnoDB: Highest supported file format is Barracuda.
2013-11-18 21:41:36 2016 [Note] InnoDB: 128 rollback segment(s) are active.
2013-11-18 21:41:36 2016 [Note] InnoDB: Waiting for purge to start
2013-11-18 21:41:36 2016 [Note] InnoDB: 5.6.11 started; log sequence number 1600624
2013-11-18 21:41:36 2016 [Note] Server hostname (bind-address): '*'; port: 3306
2013-11-18 21:41:36 2016 [Note] IPv6 is available.
2013-11-18 21:41:36 2016 [Note] - '::' resolves to '::';
2013-11-18 21:41:36 2016 [Note] Server socket created on IP: '::'.
2013-11-18 21:41:39 2016 [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-11-18 21:41:39 2016 [Warning] Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.
2013-11-18 21:41:39 2016 [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-11-18 21:41:39 2016 [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-11-18 21:41:39 2016 [Warning] Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.
2013-11-18 21:41:41 2016 [Note] Event Scheduler: Loaded 0 events
2013-11-18 21:41:41 2016 [Note] C:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.11' socket: '' port: 3306 MySQL Community Server (GPL)
2013-11-18 22:10:43 170c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-11-18 22:14:27 170c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-11-18 22:14:27 170c InnoDB: Error: Fetch of persistent statistics requested for table "ijdb"."joke" 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-11-18 22:28:50 6c0 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-11-18 22:28:50 6c0 InnoDB: Recalculation of persistent statistics requested for table "ijdb"."joke" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-11-21 13:11:38 2044 [Note] Plugin 'FEDERATED' is disabled.
2013-11-21 13:11:38 424 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-11-21 13:11:38 2044 [Note] InnoDB: The InnoDB memory heap is disabled
2013-11-21 13:11:38 2044 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-11-21 13:11:38 2044 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-11-21 13:11:38 2044 [Note] InnoDB: Not using CPU crc32 instructions
2013-11-21 13:11:39 2044 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-11-21 13:11:39 2044 [Note] InnoDB: Completed initialization of buffer pool
2013-11-21 13:11:39 2044 [Note] InnoDB: Highest supported file format is Barracuda.
2013-11-21 13:11:39 2044 [Note] InnoDB: The log sequence numbers 1600624 and 1600624 in ibdata files do not match the log sequence number 1607343 in the ib_logfiles!
2013-11-21 13:11:39 2044 [Note] InnoDB: Database was not shutdown normally!
2013-11-21 13:11:39 2044 [Note] InnoDB: Starting crash recovery.
2013-11-21 13:11:39 2044 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-11-21 13:11:39 2044 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace ijdb/joke uses space ID: 1 at filepath: .\ijdb\joke.ibd. Cannot open tablespace mysql/innodb_table_stats which uses space ID: 1 at filepath: .\mysql\innodb_table_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_table_stats.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-11-21 17:47:37 5632 [Note] Plugin 'FEDERATED' is disabled.
2013-11-21 17:47:38 14ec 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-11-21 17:47:38 5632 [Note] InnoDB: The InnoDB memory heap is disabled
2013-11-21 17:47:38 5632 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-11-21 17:47:38 5632 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-11-21 17:47:38 5632 [Note] InnoDB: Not using CPU crc32 instructions
2013-11-21 17:47:38 5632 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-11-21 17:47:38 5632 [Note] InnoDB: Completed initialization of buffer pool
2013-11-21 17:47:38 5632 [Note] InnoDB: Highest supported file format is Barracuda.
2013-11-21 17:47:38 5632 [Note] InnoDB: The log sequence numbers 1600624 and 1600624 in ibdata files do not match the log sequence number 1607343 in the ib_logfiles!
2013-11-21 17:47:38 5632 [Note] InnoDB: Database was not shutdown normally!
2013-11-21 17:47:38 5632 [Note] InnoDB: Starting crash recovery.
2013-11-21 17:47:38 5632 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-11-21 17:47:38 5632 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace ijdb/joke uses space ID: 1 at filepath: .\ijdb\joke.ibd. Cannot open tablespace mysql/innodb_table_stats which uses space ID: 1 at filepath: .\mysql\innodb_table_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_table_stats.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-11-21 17:48:01 5908 [Note] Plugin 'FEDERATED' is disabled.
2013-11-21 17:48:01 14c8 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-11-21 17:48:01 5908 [Note] InnoDB: The InnoDB memory heap is disabled
2013-11-21 17:48:01 5908 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-11-21 17:48:01 5908 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-11-21 17:48:01 5908 [Note] InnoDB: Not using CPU crc32 instructions
2013-11-21 17:48:01 5908 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-11-21 17:48:01 5908 [Note] InnoDB: Completed initialization of buffer pool
2013-11-21 17:48:01 5908 [Note] InnoDB: Highest supported file format is Barracuda.
2013-11-21 17:48:01 5908 [Note] InnoDB: The log sequence numbers 1600624 and 1600624 in ibdata files do not match the log sequence number 1607343 in the ib_logfiles!
2013-11-21 17:48:01 5908 [Note] InnoDB: Database was not shutdown normally!
2013-11-21 17:48:01 5908 [Note] InnoDB: Starting crash recovery.
2013-11-21 17:48:01 5908 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-11-21 17:48:01 5908 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace ijdb/joke uses space ID: 1 at filepath: .\ijdb\joke.ibd. Cannot open tablespace mysql/innodb_table_stats which uses space ID: 1 at filepath: .\mysql\innodb_table_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_table_stats.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-11-21 17:49:45 5848 [Note] Plugin 'FEDERATED' is disabled.
2013-11-21 17:49:45 1404 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-11-21 17:49:45 5848 [Note] InnoDB: The InnoDB memory heap is disabled
2013-11-21 17:49:45 5848 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-11-21 17:49:45 5848 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-11-21 17:49:45 5848 [Note] InnoDB: Not using CPU crc32 instructions
2013-11-21 17:49:45 5848 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-11-21 17:49:45 5848 [Note] InnoDB: Completed initialization of buffer pool
2013-11-21 17:49:45 5848 [Note] InnoDB: Highest supported file format is Barracuda.
2013-11-21 17:49:46 5848 [Note] InnoDB: The log sequence numbers 1600624 and 1600624 in ibdata files do not match the log sequence number 1607343 in the ib_logfiles!
2013-11-21 17:49:46 5848 [Note] InnoDB: Database was not shutdown normally!
2013-11-21 17:49:46 5848 [Note] InnoDB: Starting crash recovery.
2013-11-21 17:49:46 5848 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-11-21 17:49:46 5848 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace ijdb/joke uses space ID: 1 at filepath: .\ijdb\joke.ibd. Cannot open tablespace mysql/innodb_table_stats which uses space ID: 1 at filepath: .\mysql\innodb_table_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_table_stats.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-11-21 17:50:05 264 [Note] Plugin 'FEDERATED' is disabled.
2013-11-21 17:50:05 98c 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-11-21 17:50:05 264 [Note] InnoDB: The InnoDB memory heap is disabled
2013-11-21 17:50:05 264 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-11-21 17:50:05 264 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-11-21 17:50:05 264 [Note] InnoDB: Not using CPU crc32 instructions
2013-11-21 17:50:05 264 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-11-21 17:50:05 264 [Note] InnoDB: Completed initialization of buffer pool
2013-11-21 17:50:06 264 [Note] InnoDB: Highest supported file format is Barracuda.
2013-11-21 17:50:06 264 [Note] InnoDB: The log sequence numbers 1600624 and 1600624 in ibdata files do not match the log sequence number 1607343 in the ib_logfiles!
2013-11-21 17:50:06 264 [Note] InnoDB: Database was not shutdown normally!
2013-11-21 17:50:06 264 [Note] InnoDB: Starting crash recovery.
2013-11-21 17:50:06 264 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-11-21 17:50:06 264 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace ijdb/joke uses space ID: 1 at filepath: .\ijdb\joke.ibd. Cannot open tablespace mysql/innodb_table_stats which uses space ID: 1 at filepath: .\mysql\innodb_table_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_table_stats.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-11-21 17:50:20 5228 [Note] Plugin 'FEDERATED' is disabled.
2013-11-21 17:50:20 1738 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-11-21 17:50:20 5228 [Note] InnoDB: The InnoDB memory heap is disabled
2013-11-21 17:50:20 5228 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-11-21 17:50:20 5228 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-11-21 17:50:20 5228 [Note] InnoDB: Not using CPU crc32 instructions
2013-11-21 17:50:20 5228 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-11-21 17:50:20 5228 [Note] InnoDB: Completed initialization of buffer pool
2013-11-21 17:50:21 5228 [Note] InnoDB: Highest supported file format is Barracuda.
2013-11-21 17:50:21 5228 [Note] InnoDB: The log sequence numbers 1600624 and 1600624 in ibdata files do not match the log sequence number 1607343 in the ib_logfiles!
2013-11-21 17:50:21 5228 [Note] InnoDB: Database was not shutdown normally!
2013-11-21 17:50:21 5228 [Note] InnoDB: Starting crash recovery.
2013-11-21 17:50:21 5228 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-11-21 17:50:21 5228 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace ijdb/joke uses space ID: 1 at filepath: .\ijdb\joke.ibd. Cannot open tablespace mysql/innodb_table_stats which uses space ID: 1 at filepath: .\mysql\innodb_table_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_table_stats.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-11-21 17:51:01 4408 [Note] Plugin 'FEDERATED' is disabled.
2013-11-21 17:51:01 160c 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-11-21 17:51:01 4408 [Note] InnoDB: The InnoDB memory heap is disabled
2013-11-21 17:51:01 4408 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-11-21 17:51:01 4408 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-11-21 17:51:01 4408 [Note] InnoDB: Not using CPU crc32 instructions
2013-11-21 17:51:01 4408 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-11-21 17:51:01 4408 [Note] InnoDB: Completed initialization of buffer pool
2013-11-21 17:51:01 4408 [Note] InnoDB: Highest supported file format is Barracuda.
2013-11-21 17:51:01 4408 [Note] InnoDB: The log sequence numbers 1600624 and 1600624 in ibdata files do not match the log sequence number 1607343 in the ib_logfiles!
2013-11-21 17:51:01 4408 [Note] InnoDB: Database was not shutdown normally!
2013-11-21 17:51:01 4408 [Note] InnoDB: Starting crash recovery.
2013-11-21 17:51:01 4408 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-11-21 17:51:01 4408 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace ijdb/joke uses space ID: 1 at filepath: .\ijdb\joke.ibd. Cannot open tablespace mysql/innodb_table_stats which uses space ID: 1 at filepath: .\mysql\innodb_table_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_table_stats.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-11-21 17:52:18 5676 [Note] Plugin 'FEDERATED' is disabled.
2013-11-21 17:52:18 1450 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-11-21 17:52:18 5676 [Note] InnoDB: The InnoDB memory heap is disabled
2013-11-21 17:52:18 5676 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-11-21 17:52:18 5676 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-11-21 17:52:18 5676 [Note] InnoDB: Not using CPU crc32 instructions
2013-11-21 17:52:18 5676 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-11-21 17:52:18 5676 [Note] InnoDB: Completed initialization of buffer pool
2013-11-21 17:52:18 5676 [Note] InnoDB: Highest supported file format is Barracuda.
2013-11-21 17:52:19 5676 [Note] InnoDB: The log sequence numbers 1600624 and 1600624 in ibdata files do not match the log sequence number 1607343 in the ib_logfiles!
2013-11-21 17:52:19 5676 [Note] InnoDB: Database was not shutdown normally!
2013-11-21 17:52:19 5676 [Note] InnoDB: Starting crash recovery.
2013-11-21 17:52:19 5676 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-11-21 17:52:19 5676 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace ijdb/joke uses space ID: 1 at filepath: .\ijdb\joke.ibd. Cannot open tablespace mysql/innodb_table_stats which uses space ID: 1 at filepath: .\mysql\innodb_table_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_table_stats.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-11-21 17:52:22 5856 [Note] Plugin 'FEDERATED' is disabled.
2013-11-21 17:52:22 1168 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-11-21 17:52:22 5856 [Note] InnoDB: The InnoDB memory heap is disabled
2013-11-21 17:52:22 5856 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-11-21 17:52:22 5856 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-11-21 17:52:22 5856 [Note] InnoDB: Not using CPU crc32 instructions
2013-11-21 17:52:22 5856 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-11-21 17:52:22 5856 [Note] InnoDB: Completed initialization of buffer pool
2013-11-21 17:52:22 5856 [Note] InnoDB: Highest supported file format is Barracuda.
2013-11-21 17:52:22 5856 [Note] InnoDB: The log sequence numbers 1600624 and 1600624 in ibdata files do not match the log sequence number 1607343 in the ib_logfiles!
2013-11-21 17:52:22 5856 [Note] InnoDB: Database was not shutdown normally!
2013-11-21 17:52:22 5856 [Note] InnoDB: Starting crash recovery.
2013-11-21 17:52:22 5856 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-11-21 17:52:22 5856 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace ijdb/joke uses space ID: 1 at filepath: .\ijdb\joke.ibd. Cannot open tablespace mysql/innodb_table_stats which uses space ID: 1 at filepath: .\mysql\innodb_table_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_table_stats.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.
Here is the log. Please help me.
2013-11-17 22:26:59 4844 [Note] Plugin 'FEDERATED' is disabled.
2013-11-17 22:26:59 114c 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-11-17 22:26:59 4844 [Note] InnoDB: The InnoDB memory heap is disabled
2013-11-17 22:26:59 4844 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-11-17 22:26:59 4844 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-11-17 22:26:59 4844 [Note] InnoDB: Not using CPU crc32 instructions
2013-11-17 22:26:59 4844 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-11-17 22:26:59 4844 [Note] InnoDB: Completed initialization of buffer pool
2013-11-17 22:26:59 4844 [Note] InnoDB: The first specified data file C:\xampp\mysql\data\ibdata1 did not exist: a new database to be created!
2013-11-17 22:26:59 4844 [Note] InnoDB: Setting file C:\xampp\mysql\data\ibdata1 size to 10 MB
2013-11-17 22:26:59 4844 [Note] InnoDB: Database physically writes the file full: wait...
2013-11-17 22:27:00 4844 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile101 size to 5 MB
2013-11-17 22:27:00 4844 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile1 size to 5 MB
2013-11-17 22:27:01 4844 [Note] InnoDB: Renaming log file C:\xampp\mysql\data\ib_logfile101 to C:\xampp\mysql\data\ib_logfile0
2013-11-17 22:27:01 4844 [Warning] InnoDB: New log files created, LSN=45781
2013-11-17 22:27:01 4844 [Note] InnoDB: Doublewrite buffer not found: creating new
2013-11-17 22:27:01 4844 [Note] InnoDB: Doublewrite buffer created
2013-11-17 22:27:03 4844 [Note] InnoDB: 128 rollback segment(s) are active.
2013-11-17 22:27:03 4844 [Warning] InnoDB: Creating foreign key constraint system tables.
2013-11-17 22:27:04 4844 [Note] InnoDB: Foreign key constraint system tables created
2013-11-17 22:27:04 4844 [Note] InnoDB: Creating tablespace and datafile system tables.
2013-11-17 22:27:04 4844 [Note] InnoDB: Tablespace and datafile system tables created.
2013-11-17 22:27:04 4844 [Note] InnoDB: Waiting for purge to start
2013-11-17 22:27:04 4844 [Note] InnoDB: 5.6.11 started; log sequence number 0
2013-11-17 22:27:04 4844 [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: 0f03cf4f-5012-11e3-8cfc-001e687a4c8e.
2013-11-17 22:27:04 4844 [Note] Server hostname (bind-address): '*'; port: 3306
2013-11-17 22:27:04 4844 [Note] IPv6 is available.
2013-11-17 22:27:04 4844 [Note] - '::' resolves to '::';
2013-11-17 22:27:04 4844 [Note] Server socket created on IP: '::'.
2013-11-17 22:27:07 4844 [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-11-17 22:27:07 4844 [Warning] Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.
2013-11-17 22:27:07 4844 [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-11-17 22:27:07 4844 [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-11-17 22:27:07 4844 [Warning] Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.
2013-11-17 22:27:10 4844 [Note] Event Scheduler: Loaded 0 events
2013-11-17 22:27:10 4844 [Note] C:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.11' socket: '' port: 3306 MySQL Community Server (GPL)
2013-11-17 22:37:09 4844 [Note] C:\xampp\mysql\bin\mysqld.exe: Normal shutdown
2013-11-17 22:37:09 4844 [Note] Giving 0 client threads a chance to die gracefully
2013-11-17 22:37:09 4844 [Note] Event Scheduler: Purging the queue. 0 events
2013-11-17 22:37:09 4844 [Note] Shutting down slave threads
2013-11-17 22:37:09 4844 [Note] Forcefully disconnecting 0 remaining clients
2013-11-17 22:37:09 4844 [Note] Binlog end
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'partition'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_METRICS'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_CMPMEM'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_CMP'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_LOCKS'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'INNODB_TRX'
2013-11-17 22:37:09 4844 [Note] Shutting down plugin 'InnoDB'
2013-11-17 22:37:09 4844 [Note] InnoDB: FTS optimize thread exiting.
2013-11-17 22:37:09 4844 [Note] InnoDB: Starting shutdown...
2013-11-17 22:37:11 4844 [Note] InnoDB: Shutdown completed; log sequence number 1600614
2013-11-17 22:37:11 4844 [Note] Shutting down plugin 'BLACKHOLE'
2013-11-17 22:37:11 4844 [Note] Shutting down plugin 'ARCHIVE'
2013-11-17 22:37:11 4844 [Note] Shutting down plugin 'MRG_MYISAM'
2013-11-17 22:37:11 4844 [Note] Shutting down plugin 'MyISAM'
2013-11-17 22:37:11 4844 [Note] Shutting down plugin 'MEMORY'
2013-11-17 22:37:11 4844 [Note] Shutting down plugin 'CSV'
2013-11-17 22:37:11 4844 [Note] Shutting down plugin 'sha256_password'
2013-11-17 22:37:11 4844 [Note] Shutting down plugin 'mysql_old_password'
2013-11-17 22:37:11 4844 [Note] Shutting down plugin 'mysql_native_password'
2013-11-17 22:37:11 4844 [Note] Shutting down plugin 'binlog'
2013-11-17 22:37:11 4844 [Note] C:\xampp\mysql\bin\mysqld.exe: Shutdown complete
2013-11-17 22:37:12 5708 [Note] Plugin 'FEDERATED' is disabled.
2013-11-17 22:37:12 16c4 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-11-17 22:37:12 5708 [Note] InnoDB: The InnoDB memory heap is disabled
2013-11-17 22:37:12 5708 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-11-17 22:37:12 5708 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-11-17 22:37:12 5708 [Note] InnoDB: Not using CPU crc32 instructions
2013-11-17 22:37:12 5708 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-11-17 22:37:12 5708 [Note] InnoDB: Completed initialization of buffer pool
2013-11-17 22:37:12 5708 [Note] InnoDB: Highest supported file format is Barracuda.
2013-11-17 22:37:13 5708 [Note] InnoDB: 128 rollback segment(s) are active.
2013-11-17 22:37:13 5708 [Note] InnoDB: Waiting for purge to start
2013-11-17 22:37:13 5708 [Note] InnoDB: 5.6.11 started; log sequence number 1600614
2013-11-17 22:37:13 5708 [Note] Server hostname (bind-address): '*'; port: 3306
2013-11-17 22:37:13 5708 [Note] IPv6 is available.
2013-11-17 22:37:13 5708 [Note] - '::' resolves to '::';
2013-11-17 22:37:13 5708 [Note] Server socket created on IP: '::'.
2013-11-17 22:37:16 5708 [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-11-17 22:37:16 5708 [Warning] Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.
2013-11-17 22:37:16 5708 [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-11-17 22:37:16 5708 [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-11-17 22:37:16 5708 [Warning] Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.
2013-11-17 22:37:16 5708 [Note] Event Scheduler: Loaded 0 events
2013-11-17 22:37:16 5708 [Note] C:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.11' socket: '' port: 3306 MySQL Community Server (GPL)
2013-11-17 23:16:56 5708 [Note] C:\xampp\mysql\bin\mysqld.exe: Normal shutdown
2013-11-17 23:16:56 5708 [Note] Giving 0 client threads a chance to die gracefully
2013-11-17 23:16:56 5708 [Note] Event Scheduler: Purging the queue. 0 events
2013-11-17 23:16:56 5708 [Note] Shutting down slave threads
2013-11-17 23:16:56 5708 [Note] Forcefully disconnecting 0 remaining clients
2013-11-17 23:16:56 5708 [Note] Binlog end
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'partition'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_METRICS'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_CMPMEM'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_CMP'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_LOCKS'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'INNODB_TRX'
2013-11-17 23:16:56 5708 [Note] Shutting down plugin 'InnoDB'
2013-11-17 23:16:56 5708 [Note] InnoDB: FTS optimize thread exiting.
2013-11-17 23:16:56 5708 [Note] InnoDB: Starting shutdown...
2013-11-17 23:17:12 5708 [Note] InnoDB: Shutdown completed; log sequence number 1600624
2013-11-17 23:17:12 5708 [Note] Shutting down plugin 'BLACKHOLE'
2013-11-17 23:17:12 5708 [Note] Shutting down plugin 'ARCHIVE'
2013-11-17 23:17:12 5708 [Note] Shutting down plugin 'MRG_MYISAM'
2013-11-17 23:17:12 5708 [Note] Shutting down plugin 'MyISAM'
2013-11-17 23:17:12 5708 [Note] Shutting down plugin 'MEMORY'
2013-11-17 23:17:12 5708 [Note] Shutting down plugin 'CSV'
2013-11-17 23:17:12 5708 [Note] Shutting down plugin 'sha256_password'
2013-11-17 23:17:12 5708 [Note] Shutting down plugin 'mysql_old_password'
2013-11-17 23:17:12 5708 [Note] Shutting down plugin 'mysql_native_password'
2013-11-17 23:17:12 5708 [Note] Shutting down plugin 'binlog'
2013-11-17 23:17:13 5708 [Note] C:\xampp\mysql\bin\mysqld.exe: Shutdown complete
2013-11-18 21:41:33 2016 [Note] Plugin 'FEDERATED' is disabled.
2013-11-18 21:41:33 7ec 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-11-18 21:41:33 2016 [Note] InnoDB: The InnoDB memory heap is disabled
2013-11-18 21:41:33 2016 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-11-18 21:41:33 2016 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-11-18 21:41:34 2016 [Note] InnoDB: Not using CPU crc32 instructions
2013-11-18 21:41:34 2016 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-11-18 21:41:34 2016 [Note] InnoDB: Completed initialization of buffer pool
2013-11-18 21:41:34 2016 [Note] InnoDB: Highest supported file format is Barracuda.
2013-11-18 21:41:36 2016 [Note] InnoDB: 128 rollback segment(s) are active.
2013-11-18 21:41:36 2016 [Note] InnoDB: Waiting for purge to start
2013-11-18 21:41:36 2016 [Note] InnoDB: 5.6.11 started; log sequence number 1600624
2013-11-18 21:41:36 2016 [Note] Server hostname (bind-address): '*'; port: 3306
2013-11-18 21:41:36 2016 [Note] IPv6 is available.
2013-11-18 21:41:36 2016 [Note] - '::' resolves to '::';
2013-11-18 21:41:36 2016 [Note] Server socket created on IP: '::'.
2013-11-18 21:41:39 2016 [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-11-18 21:41:39 2016 [Warning] Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.
2013-11-18 21:41:39 2016 [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-11-18 21:41:39 2016 [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-11-18 21:41:39 2016 [Warning] Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.
2013-11-18 21:41:41 2016 [Note] Event Scheduler: Loaded 0 events
2013-11-18 21:41:41 2016 [Note] C:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.11' socket: '' port: 3306 MySQL Community Server (GPL)
2013-11-18 22:10:43 170c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-11-18 22:14:27 170c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-11-18 22:14:27 170c InnoDB: Error: Fetch of persistent statistics requested for table "ijdb"."joke" 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-11-18 22:28:50 6c0 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-11-18 22:28:50 6c0 InnoDB: Recalculation of persistent statistics requested for table "ijdb"."joke" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-11-21 13:11:38 2044 [Note] Plugin 'FEDERATED' is disabled.
2013-11-21 13:11:38 424 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-11-21 13:11:38 2044 [Note] InnoDB: The InnoDB memory heap is disabled
2013-11-21 13:11:38 2044 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-11-21 13:11:38 2044 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-11-21 13:11:38 2044 [Note] InnoDB: Not using CPU crc32 instructions
2013-11-21 13:11:39 2044 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-11-21 13:11:39 2044 [Note] InnoDB: Completed initialization of buffer pool
2013-11-21 13:11:39 2044 [Note] InnoDB: Highest supported file format is Barracuda.
2013-11-21 13:11:39 2044 [Note] InnoDB: The log sequence numbers 1600624 and 1600624 in ibdata files do not match the log sequence number 1607343 in the ib_logfiles!
2013-11-21 13:11:39 2044 [Note] InnoDB: Database was not shutdown normally!
2013-11-21 13:11:39 2044 [Note] InnoDB: Starting crash recovery.
2013-11-21 13:11:39 2044 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-11-21 13:11:39 2044 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace ijdb/joke uses space ID: 1 at filepath: .\ijdb\joke.ibd. Cannot open tablespace mysql/innodb_table_stats which uses space ID: 1 at filepath: .\mysql\innodb_table_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_table_stats.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-11-21 17:47:37 5632 [Note] Plugin 'FEDERATED' is disabled.
2013-11-21 17:47:38 14ec 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-11-21 17:47:38 5632 [Note] InnoDB: The InnoDB memory heap is disabled
2013-11-21 17:47:38 5632 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-11-21 17:47:38 5632 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-11-21 17:47:38 5632 [Note] InnoDB: Not using CPU crc32 instructions
2013-11-21 17:47:38 5632 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-11-21 17:47:38 5632 [Note] InnoDB: Completed initialization of buffer pool
2013-11-21 17:47:38 5632 [Note] InnoDB: Highest supported file format is Barracuda.
2013-11-21 17:47:38 5632 [Note] InnoDB: The log sequence numbers 1600624 and 1600624 in ibdata files do not match the log sequence number 1607343 in the ib_logfiles!
2013-11-21 17:47:38 5632 [Note] InnoDB: Database was not shutdown normally!
2013-11-21 17:47:38 5632 [Note] InnoDB: Starting crash recovery.
2013-11-21 17:47:38 5632 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-11-21 17:47:38 5632 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace ijdb/joke uses space ID: 1 at filepath: .\ijdb\joke.ibd. Cannot open tablespace mysql/innodb_table_stats which uses space ID: 1 at filepath: .\mysql\innodb_table_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_table_stats.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-11-21 17:48:01 5908 [Note] Plugin 'FEDERATED' is disabled.
2013-11-21 17:48:01 14c8 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-11-21 17:48:01 5908 [Note] InnoDB: The InnoDB memory heap is disabled
2013-11-21 17:48:01 5908 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-11-21 17:48:01 5908 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-11-21 17:48:01 5908 [Note] InnoDB: Not using CPU crc32 instructions
2013-11-21 17:48:01 5908 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-11-21 17:48:01 5908 [Note] InnoDB: Completed initialization of buffer pool
2013-11-21 17:48:01 5908 [Note] InnoDB: Highest supported file format is Barracuda.
2013-11-21 17:48:01 5908 [Note] InnoDB: The log sequence numbers 1600624 and 1600624 in ibdata files do not match the log sequence number 1607343 in the ib_logfiles!
2013-11-21 17:48:01 5908 [Note] InnoDB: Database was not shutdown normally!
2013-11-21 17:48:01 5908 [Note] InnoDB: Starting crash recovery.
2013-11-21 17:48:01 5908 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-11-21 17:48:01 5908 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace ijdb/joke uses space ID: 1 at filepath: .\ijdb\joke.ibd. Cannot open tablespace mysql/innodb_table_stats which uses space ID: 1 at filepath: .\mysql\innodb_table_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_table_stats.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-11-21 17:49:45 5848 [Note] Plugin 'FEDERATED' is disabled.
2013-11-21 17:49:45 1404 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-11-21 17:49:45 5848 [Note] InnoDB: The InnoDB memory heap is disabled
2013-11-21 17:49:45 5848 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-11-21 17:49:45 5848 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-11-21 17:49:45 5848 [Note] InnoDB: Not using CPU crc32 instructions
2013-11-21 17:49:45 5848 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-11-21 17:49:45 5848 [Note] InnoDB: Completed initialization of buffer pool
2013-11-21 17:49:45 5848 [Note] InnoDB: Highest supported file format is Barracuda.
2013-11-21 17:49:46 5848 [Note] InnoDB: The log sequence numbers 1600624 and 1600624 in ibdata files do not match the log sequence number 1607343 in the ib_logfiles!
2013-11-21 17:49:46 5848 [Note] InnoDB: Database was not shutdown normally!
2013-11-21 17:49:46 5848 [Note] InnoDB: Starting crash recovery.
2013-11-21 17:49:46 5848 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-11-21 17:49:46 5848 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace ijdb/joke uses space ID: 1 at filepath: .\ijdb\joke.ibd. Cannot open tablespace mysql/innodb_table_stats which uses space ID: 1 at filepath: .\mysql\innodb_table_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_table_stats.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-11-21 17:50:05 264 [Note] Plugin 'FEDERATED' is disabled.
2013-11-21 17:50:05 98c 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-11-21 17:50:05 264 [Note] InnoDB: The InnoDB memory heap is disabled
2013-11-21 17:50:05 264 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-11-21 17:50:05 264 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-11-21 17:50:05 264 [Note] InnoDB: Not using CPU crc32 instructions
2013-11-21 17:50:05 264 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-11-21 17:50:05 264 [Note] InnoDB: Completed initialization of buffer pool
2013-11-21 17:50:06 264 [Note] InnoDB: Highest supported file format is Barracuda.
2013-11-21 17:50:06 264 [Note] InnoDB: The log sequence numbers 1600624 and 1600624 in ibdata files do not match the log sequence number 1607343 in the ib_logfiles!
2013-11-21 17:50:06 264 [Note] InnoDB: Database was not shutdown normally!
2013-11-21 17:50:06 264 [Note] InnoDB: Starting crash recovery.
2013-11-21 17:50:06 264 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-11-21 17:50:06 264 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace ijdb/joke uses space ID: 1 at filepath: .\ijdb\joke.ibd. Cannot open tablespace mysql/innodb_table_stats which uses space ID: 1 at filepath: .\mysql\innodb_table_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_table_stats.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-11-21 17:50:20 5228 [Note] Plugin 'FEDERATED' is disabled.
2013-11-21 17:50:20 1738 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-11-21 17:50:20 5228 [Note] InnoDB: The InnoDB memory heap is disabled
2013-11-21 17:50:20 5228 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-11-21 17:50:20 5228 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-11-21 17:50:20 5228 [Note] InnoDB: Not using CPU crc32 instructions
2013-11-21 17:50:20 5228 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-11-21 17:50:20 5228 [Note] InnoDB: Completed initialization of buffer pool
2013-11-21 17:50:21 5228 [Note] InnoDB: Highest supported file format is Barracuda.
2013-11-21 17:50:21 5228 [Note] InnoDB: The log sequence numbers 1600624 and 1600624 in ibdata files do not match the log sequence number 1607343 in the ib_logfiles!
2013-11-21 17:50:21 5228 [Note] InnoDB: Database was not shutdown normally!
2013-11-21 17:50:21 5228 [Note] InnoDB: Starting crash recovery.
2013-11-21 17:50:21 5228 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-11-21 17:50:21 5228 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace ijdb/joke uses space ID: 1 at filepath: .\ijdb\joke.ibd. Cannot open tablespace mysql/innodb_table_stats which uses space ID: 1 at filepath: .\mysql\innodb_table_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_table_stats.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-11-21 17:51:01 4408 [Note] Plugin 'FEDERATED' is disabled.
2013-11-21 17:51:01 160c 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-11-21 17:51:01 4408 [Note] InnoDB: The InnoDB memory heap is disabled
2013-11-21 17:51:01 4408 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-11-21 17:51:01 4408 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-11-21 17:51:01 4408 [Note] InnoDB: Not using CPU crc32 instructions
2013-11-21 17:51:01 4408 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-11-21 17:51:01 4408 [Note] InnoDB: Completed initialization of buffer pool
2013-11-21 17:51:01 4408 [Note] InnoDB: Highest supported file format is Barracuda.
2013-11-21 17:51:01 4408 [Note] InnoDB: The log sequence numbers 1600624 and 1600624 in ibdata files do not match the log sequence number 1607343 in the ib_logfiles!
2013-11-21 17:51:01 4408 [Note] InnoDB: Database was not shutdown normally!
2013-11-21 17:51:01 4408 [Note] InnoDB: Starting crash recovery.
2013-11-21 17:51:01 4408 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-11-21 17:51:01 4408 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace ijdb/joke uses space ID: 1 at filepath: .\ijdb\joke.ibd. Cannot open tablespace mysql/innodb_table_stats which uses space ID: 1 at filepath: .\mysql\innodb_table_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_table_stats.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-11-21 17:52:18 5676 [Note] Plugin 'FEDERATED' is disabled.
2013-11-21 17:52:18 1450 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-11-21 17:52:18 5676 [Note] InnoDB: The InnoDB memory heap is disabled
2013-11-21 17:52:18 5676 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-11-21 17:52:18 5676 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-11-21 17:52:18 5676 [Note] InnoDB: Not using CPU crc32 instructions
2013-11-21 17:52:18 5676 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-11-21 17:52:18 5676 [Note] InnoDB: Completed initialization of buffer pool
2013-11-21 17:52:18 5676 [Note] InnoDB: Highest supported file format is Barracuda.
2013-11-21 17:52:19 5676 [Note] InnoDB: The log sequence numbers 1600624 and 1600624 in ibdata files do not match the log sequence number 1607343 in the ib_logfiles!
2013-11-21 17:52:19 5676 [Note] InnoDB: Database was not shutdown normally!
2013-11-21 17:52:19 5676 [Note] InnoDB: Starting crash recovery.
2013-11-21 17:52:19 5676 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-11-21 17:52:19 5676 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace ijdb/joke uses space ID: 1 at filepath: .\ijdb\joke.ibd. Cannot open tablespace mysql/innodb_table_stats which uses space ID: 1 at filepath: .\mysql\innodb_table_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_table_stats.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-11-21 17:52:22 5856 [Note] Plugin 'FEDERATED' is disabled.
2013-11-21 17:52:22 1168 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-11-21 17:52:22 5856 [Note] InnoDB: The InnoDB memory heap is disabled
2013-11-21 17:52:22 5856 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-11-21 17:52:22 5856 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-11-21 17:52:22 5856 [Note] InnoDB: Not using CPU crc32 instructions
2013-11-21 17:52:22 5856 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-11-21 17:52:22 5856 [Note] InnoDB: Completed initialization of buffer pool
2013-11-21 17:52:22 5856 [Note] InnoDB: Highest supported file format is Barracuda.
2013-11-21 17:52:22 5856 [Note] InnoDB: The log sequence numbers 1600624 and 1600624 in ibdata files do not match the log sequence number 1607343 in the ib_logfiles!
2013-11-21 17:52:22 5856 [Note] InnoDB: Database was not shutdown normally!
2013-11-21 17:52:22 5856 [Note] InnoDB: Starting crash recovery.
2013-11-21 17:52:22 5856 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-11-21 17:52:22 5856 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace ijdb/joke uses space ID: 1 at filepath: .\ijdb\joke.ibd. Cannot open tablespace mysql/innodb_table_stats which uses space ID: 1 at filepath: .\mysql\innodb_table_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_table_stats.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.