2013-10-19 06:50:53 3712 [Note] Plugin 'FEDERATED' is disabled.
2013-10-19 06:50:53 3712 [Note] InnoDB: The InnoDB memory heap is disabled
2013-10-19 06:50:53 3712 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-10-19 06:50:53 3712 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-10-19 06:50:53 3712 [Note] InnoDB: Not using CPU crc32 instructions
2013-10-19 06:50:53 3712 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2013-10-19 06:50:53 3712 [Note] InnoDB: Completed initialization of buffer pool
2013-10-19 06:50:53 3712 [Note] InnoDB: Highest supported file format is Barracuda.
2013-10-19 06:50:53 3712 [Note] InnoDB: The log sequence numbers 1631613 and 1631613 in ibdata files do not match the log sequence number 2733317 in the ib_logfiles!
2013-10-19 06:50:53 3712 [Note] InnoDB: Database was not shutdown normally!
2013-10-19 06:50:53 3712 [Note] InnoDB: Starting crash recovery.
2013-10-19 06:50:53 3712 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-10-19 06:50:53 3712 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace gazelle/api_applications uses space ID: 5 at filepath: .\gazelle\api_applications.ibd. Cannot open tablespace mysql/slave_worker_info which uses space ID: 5 at filepath: .\mysql\slave_worker_info.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\slave_worker_info.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.