MySQL will not restart

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

MySQL will not restart

Postby tntitan » 30. August 2015 00:35

After installing the latest version of xampp, I had to change the port on apache. But mysql started with no problems. But after closing xampp and restarting, Apache starts OK but I can't get MySQL to start. I keep getting the following error(log follows):
6:33:45 PM [main] Initializing Control Panel
6:33:45 PM [main] Windows Version: Windows 8 64-bit
6:33:45 PM [main] XAMPP Version: 5.6.12
6:33:45 PM [main] Control Panel Version: 3.2.1 [ Compiled: May 7th 2013 ]
6:33:45 PM [main] Running with Administrator rights - good!
6:33:45 PM [main] XAMPP Installation Directory: "c:\xampp\"
6:33:45 PM [main] Checking for prerequisites
6:33:45 PM [main] All prerequisites found
6:33:45 PM [main] Initializing Modules
6:33:45 PM [main] The FileZilla module is disabled
6:33:45 PM [main] The Mercury module is disabled
6:33:45 PM [main] The Tomcat module is disabled
6:33:45 PM [main] Starting Check-Timer
6:33:45 PM [main] Control Panel Ready
6:33:50 PM [Apache] Attempting to start Apache app...
6:33:50 PM [Apache] Status change detected: running
6:34:03 PM [mysql] Attempting to start MySQL app...
6:34:03 PM [mysql] Status change detected: running
6:34:04 PM [mysql] Status change detected: stopped
6:34:04 PM [mysql] Error: MySQL shutdown unexpectedly.
6:34:04 PM [mysql] This may be due to a blocked port, missing dependencies,
6:34:04 PM [mysql] improper privileges, a crash, or a shutdown by another method.
6:34:04 PM [mysql] Press the Logs button to view error logs and check
6:34:04 PM [mysql] the Windows Event Viewer for more clues
6:34:04 PM [mysql] If you need more help, copy and post this
6:34:04 PM [mysql] entire log window on the forums

2015-08-29 18:21:39 7204 [Note] Plugin 'FEDERATED' is disabled.
2015-08-29 18:21:39 15e8 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-08-29 18:21:39 7204 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-08-29 18:21:39 7204 [Note] InnoDB: The InnoDB memory heap is disabled
2015-08-29 18:21:39 7204 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-08-29 18:21:39 7204 [Note] InnoDB: Memory barrier is not used
2015-08-29 18:21:39 7204 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-08-29 18:21:39 7204 [Note] InnoDB: Not using CPU crc32 instructions
2015-08-29 18:21:39 7204 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-08-29 18:21:39 7204 [Note] InnoDB: Completed initialization of buffer pool
2015-08-29 18:21:39 7204 [Note] InnoDB: Highest supported file format is Barracuda.
2015-08-29 18:21:39 7204 [Note] InnoDB: The log sequence numbers 1665234 and 1665234 in ibdata files do not match the log sequence number 1665254 in the ib_logfiles!
2015-08-29 18:21:39 7204 [Note] InnoDB: Database was not shutdown normally!
2015-08-29 18:21:39 7204 [Note] InnoDB: Starting crash recovery.
2015-08-29 18:21:39 7204 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-08-29 18:21:39 7204 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace phpmyadmin/pma_navigationhiding uses space ID: 8 at filepath: .\phpmyadmin\pma_navigationhiding.ibd. Cannot open tablespace wordpress1/wp_terms which uses space ID: 8 at filepath: .\wordpress1\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\wordpress1\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.
Posts: 1
Joined: 31. January 2015 19:09
Operating System: Windows 10

Return to XAMPP for Windows

Who is online

Users browsing this forum: No registered users and 72 guests