Can't Start Apache or MySQL

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

Can't Start Apache or MySQL

Postby redf150flames » 10. January 2017 21:42

I'm getting the following errors when I try to start Apache and MySQL

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


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

And this is the only error I find from when I tried starting them:

2017-01-10 12:45:07 27b8 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.
2017-01-10 12:45:07 10168 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-01-10 12:45:07 10168 [Note] InnoDB: The InnoDB memory heap is disabled
2017-01-10 12:45:07 10168 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-01-10 12:45:07 10168 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-01-10 12:45:07 10168 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-01-10 12:45:07 10168 [Note] InnoDB: Using generic crc32 instructions
2017-01-10 12:45:07 10168 [Note] InnoDB: Initializing buffer pool, size = 20.0M
2017-01-10 12:45:07 10168 [Note] InnoDB: Completed initialization of buffer pool
2017-01-10 12:45:07 10168 [Note] InnoDB: Highest supported file format is Barracuda.
2017-01-10 12:45:07 10168 [Note] InnoDB: The log sequence numbers 3109477 and 3109477 in ibdata files do not match the log sequence number 14050130 in the ib_logfiles!
2017-01-10 12:45:07 10168 [Note] InnoDB: Database was not shutdown normally!
2017-01-10 12:45:07 10168 [Note] InnoDB: Starting crash recovery.
2017-01-10 12:45:07 10168 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-01-10 12:45:07 10168 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace amsoil/wp_comments-DESKTOP-7V1BDFV uses space ID: 37 at filepath: .\amsoil\wp_comments-desktop-7v1bdfv.ibd. Cannot open tablespace amsoil/wp_comments which uses space ID: 37 at filepath: .\amsoil\wp_comments.ibd
InnoDB: Error: could not open single-table tablespace file .\amsoil\wp_comments.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.

Any ideas how to fix this?

Thank you!
redf150flames
 
Posts: 1
Joined: 10. January 2017 21:37
Location: California
XAMPP version: 3.2.2
Operating System: Windows 10

Return to XAMPP for Windows

Who is online

Users browsing this forum: No registered users and 41 guests