Sql Crash

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

Sql Crash

Postby ehouston » 14. December 2017 12:15

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


2017-12-14 02:47:10 1474 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-12-14 2:47:10 5236 [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-12-14 2:47:10 5236 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-12-14 2:47:10 5236 [Note] InnoDB: The InnoDB memory heap is disabled
2017-12-14 2:47:10 5236 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-12-14 2:47:10 5236 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-12-14 2:47:10 5236 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-12-14 2:47:10 5236 [Note] InnoDB: Using generic crc32 instructions
2017-12-14 2:47:10 5236 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-12-14 2:47:10 5236 [Note] InnoDB: Completed initialization of buffer pool
2017-12-14 2:47:10 5236 [Note] InnoDB: Restoring page 0 of tablespace 0
2017-12-14 2:47:10 5236 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0
2017-12-14 2:47:10 5236 [ERROR] InnoDB: space header page consists of zero bytes in data file C:\xampp\mysql\data\ibdata1
2017-12-14 2:47:10 5236 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
2017-12-14 2:47:10 5236 [ERROR] Plugin 'InnoDB' init function returned error.
2017-12-14 2:47:10 5236 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
Cannot find checkpoint record at LSN (1,0x208b)

2017-12-14 2:47:10 5236 [ERROR] mysqld.exe: Aria recovery failed. Please run aria_chk -r on all Aria tables and delete all aria_log.######## files
2017-12-14 2:47:10 5236 [ERROR] Plugin 'Aria' init function returned error.
2017-12-14 2:47:10 5236 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
2017-12-14 2:47:10 5236 [Note] Plugin 'FEEDBACK' is disabled.
2017-12-14 2:47:10 5236 [ERROR] Unknown/unsupported storage engine: InnoDB
2017-12-14 2:47:10 5236 [ERROR] Aborting
Posts: 1
Joined: 14. December 2017 12:07
XAMPP version: 7.1.11
Operating System: Windows 10

Return to XAMPP for Windows

Who is online

Users browsing this forum: No registered users and 37 guests