2015-05-20 10:48:47 5920 [Note] Plugin 'FEDERATED' is disabled.
2015-05-20 10:48:47 8dc 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.
2015-05-20 10:48:47 5920 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-05-20 10:48:47 5920 [Note] InnoDB: The InnoDB memory heap is disabled
2015-05-20 10:48:47 5920 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-05-20 10:48:47 5920 [Note] InnoDB: Memory barrier is not used
2015-05-20 10:48:47 5920 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-05-20 10:48:47 5920 [Note] InnoDB: Not using CPU crc32 instructions
2015-05-20 10:48:47 5920 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-05-20 10:48:47 5920 [Note] InnoDB: Completed initialization of buffer pool
2015-05-20 10:48:47 5920 [Note] InnoDB: Highest supported file format is Barracuda.
2015-05-20 10:48:47 5920 [Note] InnoDB: 128 rollback segment(s) are active.
2015-05-20 10:48:48 5920 [Note] InnoDB: Waiting for purge to start
2015-05-20 10:48:48 5920 [Note] InnoDB: 5.6.21 started; log sequence number 1665234
2015-05-20 10:48:48 5920 [Note] Server hostname (bind-address): '*'; port: 3306
2015-05-20 10:48:48 5920 [Note] IPv6 is available.
2015-05-20 10:48:48 5920 [Note] - '::' resolves to '::';
2015-05-20 10:48:48 5920 [Note] Server socket created on IP: '::'.
2015-05-20 10:54:10 2708 [Note] Plugin 'FEDERATED' is disabled.
2015-05-20 10:54:10 3f8 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.
2015-05-20 10:54:10 2708 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-05-20 10:54:10 2708 [Note] InnoDB: The InnoDB memory heap is disabled
2015-05-20 10:54:10 2708 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-05-20 10:54:10 2708 [Note] InnoDB: Memory barrier is not used
2015-05-20 10:54:10 2708 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-05-20 10:54:10 2708 [Note] InnoDB: Not using CPU crc32 instructions
2015-05-20 10:54:10 2708 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-05-20 10:54:10 2708 [Note] InnoDB: Completed initialization of buffer pool
2015-05-20 10:54:10 2708 [Note] InnoDB: Highest supported file format is Barracuda.
2015-05-20 10:54:10 2708 [Note] InnoDB: The log sequence numbers 1665234 and 1665234 in ibdata files do not match the log sequence number 1665244 in the ib_logfiles!
2015-05-20 10:54:10 2708 [Note] InnoDB: Database was not shutdown normally!
2015-05-20 10:54:10 2708 [Note] InnoDB: Starting crash recovery.
2015-05-20 10:54:10 2708 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-05-20 10:54:10 2708 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_index_stats uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd. Cannot open tablespace mysql/innodb_index_stats.Id_63049 which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.id_63049.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.id_63049.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.
2015-05-20 16:05:02 128 [Note] Plugin 'FEDERATED' is disabled.
2015-05-20 16:05:02 d48 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.
2015-05-20 16:05:02 128 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-05-20 16:05:02 128 [Note] InnoDB: The InnoDB memory heap is disabled
2015-05-20 16:05:02 128 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-05-20 16:05:02 128 [Note] InnoDB: Memory barrier is not used
2015-05-20 16:05:02 128 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-05-20 16:05:02 128 [Note] InnoDB: Not using CPU crc32 instructions
2015-05-20 16:05:02 128 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-05-20 16:05:02 128 [Note] InnoDB: Completed initialization of buffer pool
2015-05-20 16:05:02 128 [Note] InnoDB: Highest supported file format is Barracuda.
2015-05-20 16:05:02 128 [Note] InnoDB: The log sequence numbers 1665234 and 1665234 in ibdata files do not match the log sequence number 1665244 in the ib_logfiles!
2015-05-20 16:05:02 128 [Note] InnoDB: Database was not shutdown normally!
2015-05-20 16:05:02 128 [Note] InnoDB: Starting crash recovery.
2015-05-20 16:05:02 128 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-05-20 16:05:02 128 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_index_stats uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd. Cannot open tablespace mysql/innodb_index_stats.Id_63049 which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.id_63049.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.id_63049.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.