Error: MySQL shutdown unexpectedly

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

Error: MySQL shutdown unexpectedly

Postby PaulC2K » 20. September 2017 10:31

I've been having issues with an update from a PHP 5.6 version, to that latest version available, and after numerous attempts at installing & reinstalling (earlier attempts dumping old files on top), im simply trying to get a fresh installation to run, but it wont.

Control Panel v3.2.2 says:
Code: Select all
10:40:46  [mysql]    Error: MySQL shutdown unexpectedly.
10:40:46  [mysql]    This may be due to a blocked port, missing dependencies,
10:40:46  [mysql]    improper privileges, a crash, or a shutdown by another method.
10:40:46  [mysql]    Press the Logs button to view error logs and check
10:40:46  [mysql]    the Windows Event Viewer for more clues
10:40:46  [mysql]    If you need more help, copy and post this
10:40:46  [mysql]    entire log window on the forums

\mysql\data\mysql_error.log says:
Code: Select all
2017-09-20 10:40:41 1b90 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-09-20 10:40:41 7056 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2017-09-20 10:40:41 7056 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-09-20 10:40:41 7056 [Note] InnoDB: The InnoDB memory heap is disabled
2017-09-20 10:40:41 7056 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-09-20 10:40:41 7056 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-09-20 10:40:41 7056 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-09-20 10:40:41 7056 [Note] InnoDB: Using generic crc32 instructions
2017-09-20 10:40:41 7056 [Note] InnoDB: Initializing buffer pool, size = 64.0M
2017-09-20 10:40:41 7056 [Note] InnoDB: Completed initialization of buffer pool
2017-09-20 10:40:41 7056 [ERROR] InnoDB: D:\xampp\mysql\data\ibdata1 can't be opened in read-write mode
2017-09-20 10:40:41 7056 [ERROR] InnoDB: The system tablespace must be writable!
2017-09-20 10:40:41 7056 [ERROR] Plugin 'InnoDB' init function returned error.
2017-09-20 10:40:41 7056 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-09-20 10:40:41 7056 [Note] Plugin 'FEEDBACK' is disabled.
2017-09-20 10:40:41 7056 [ERROR] Unknown/unsupported storage engine: InnoDB
2017-09-20 10:40:41 7056 [ERROR] Aborting

Running xampp_start.exe im able to load up the dashboard, and with files copied across im able to access local sites as normal, so its not entirely broken, however i cant understand why the control panel cannot launch the MySQL portion, as i'd much rather let this control everything. I've tried running as administrator on the off chance it helps, but no such luck, and google gives so many varied results and i cant pin down exactly what part of the error to search for to get the answer i need.

The error log makes little sense to me, i dont mind getting my hands dirty, i just havent got a clue what its. The error talks of increasing buffer pool to at least 20MB, ive figured out what its referring to and used: innodb_buffer_pool_size = 64M, restarted Apache (just in case) and MySQL starts but stops shortly after. It mentions having 64.0M in the error, but still asks for at least 20MB, making me wonder if these are the different values and im just changing something else.

What is it trying to ask me to do?? I should have been asleep about 8hrs ago, but instead im pulling my hair out with this.
Posts: 8
Joined: 28. July 2010 03:26
XAMPP version: PHP 7.1.9
Operating System: Win10

Return to XAMPP for Windows

Who is online

Users browsing this forum: No registered users and 46 guests