MySQL isn't Running in Win7 64 bit

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

MySQL isn't Running in Win7 64 bit

Postby azizultex » 08. August 2014 03:27

Hi there,
I see below error when I try to start MySQL :

8:21:49 AM [mysql] Error: MySQL shutdown unexpectedly.
8:21:49 AM [mysql] This may be due to a blocked port, missing dependencies,
8:21:49 AM [mysql] improper privileges, a crash, or a shutdown by another method.
8:21:49 AM [mysql] Press the Logs button to view error logs and check
8:21:49 AM [mysql] the Windows Event Viewer for more clues
8:21:49 AM [mysql] If you need more help, copy and post this
8:21:49 AM [mysql] entire log window on the forums

In the error log, I can see below description:

2014-08-08 08:21:55 3588 [Note] Plugin 'FEDERATED' is disabled.
2014-08-08 08:21:55 47c 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.
2014-08-08 08:21:55 3588 [Note] InnoDB: The InnoDB memory heap is disabled
2014-08-08 08:21:55 3588 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-08-08 08:21:55 3588 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-08-08 08:21:55 3588 [Note] InnoDB: Not using CPU crc32 instructions
2014-08-08 08:21:55 3588 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-08-08 08:21:55 3588 [Note] InnoDB: Completed initialization of buffer pool
2014-08-08 08:21:55 3588 [Note] InnoDB: Highest supported file format is Barracuda.
2014-08-08 08:21:55 3588 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2930446 in the ib_logfiles!
2014-08-08 08:21:55 3588 [Note] InnoDB: Database was not shutdown normally!
2014-08-08 08:21:55 3588 [Note] InnoDB: Starting crash recovery.
2014-08-08 08:21:55 3588 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-08-08 08:21:55 3588 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace envatobd/wp_usermeta uses space ID: 2 at filepath: .\envatobd\wp_usermeta.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_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.

Please help me how I can start MySQL. I need help asap

Posts: 8
Joined: 19. July 2013 15:30
XAMPP Version: 5.6.3
Operating System: Windows

Return to XAMPP for Windows

Who is online

Users browsing this forum: Altrea and 77 guests