Error: MySQL shutdown unexpectedly.

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

Error: MySQL shutdown unexpectedly.

Postby eddwatts » 26. August 2017 02:09

I started having this problem when I installed Mamp for windows.

This is the error log


2017-08-25 20:18:12 14184 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-08-25 20:18:12 14184 [Note] InnoDB: The InnoDB memory heap is disabled
2017-08-25 20:18:12 14184 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-08-25 20:18:12 14184 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-08-25 20:18:12 14184 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-08-25 20:18:12 14184 [Note] InnoDB: Using generic crc32 instructions
2017-08-25 20:18:12 14184 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-08-25 20:18:12 14184 [Note] InnoDB: Completed initialization of buffer pool
2017-08-25 20:18:12 14184 [Note] InnoDB: Highest supported file format is Barracuda.
2017-08-25 20:18:12 14184 [Note] InnoDB: The log sequence number 1835037 in ibdata file do not match the log sequence number 29892011 in the ib_logfiles!
2017-08-25 20:18:12 14184 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace gizmoelperro/wp_term_taxonomy uses space ID: 10 at filepath: .\gizmoelperro\wp_term_taxonomy.ibd. Cannot open tablespace mysql/gtid_slave_pos which uses space ID: 10 at filepath: .\mysql\gtid_slave_pos.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\gtid_slave_pos.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.
170825 20:18:12 [ERROR] mysqld got exception 0x80000003 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware
eddwatts
 
Posts: 1
Joined: 26. August 2017 02:05
XAMPP version: 3.2.2
Operating System: Windows 10

Re: Error: MySQL shutdown unexpectedly.

Postby Nobbie » 26. August 2017 09:32

eddwatts wrote:I started having this problem when I installed Mamp for windows.


You accidently joined the wrong forum, this is *NOT* the MAMP forum, but instead the XAMPP forum. XAMPP is another webserver distribution. You should move to a MAMP forum.
Nobbie
 
Posts: 9628
Joined: 09. March 2008 13:04


Return to XAMPP for Windows

Who is online

Users browsing this forum: No registered users and 41 guests