Error: MySQL shutdown unexpectedly XAMPP

1

When I open XAMPP and click on Start MySQL, it gives me the following error, even though it used to work correctly

  

03:17:20 p.m. [mysql] Error: MySQL shutdown unexpectedly.

     

03:17:20 p.m. [mysql] This may be due to blocked port, missing dependencies,

     

03:17:20 p.m. [mysql] improper privileges, to crash, or to shutdown by another method.

     

03:17:20 p.m. [mysql] Press the Logs button to view error logs and check

     

03:17:20 p.m. [mysql] the Windows Event Viewer for more clues

     

03:17:20 p.m. [mysql] If you need more help, copy and post this

     

03:17:20 p.m. [mysql] entire log window on the forums

The error that appears in logs is the following:

  

2017-06-05 16:46:03 92c 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-06-05 16:46:03 2348 [Note] InnoDB: Using mutexes to ref count buffer pool pages

     

2017-06-05 16:46:03 2348 [Note] InnoDB: The InnoDB memory heap is disabled

     

2017-06-05 16:46:03 2348 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions

     

2017-06-05 16:46:03 2348 [Note] InnoDB: Memory barrier is not used

     

2017-06-05 16:46:03 2348 [Note] InnoDB: Compressed tables use zlib 1.2.3

     

2017-06-05 16:46:03 2348 [Note] InnoDB: Using generic crc32 instructions

     

2017-06-05 16:46:03 2348 [Note] InnoDB: Initializing buffer pool, size = 16.0M

     

2017-06-05 16:46:03 2348 [Note] InnoDB: Completed initialization of buffer pool

     

2017-06-05 16:46:03 2348 [Note] InnoDB: Restoring page 0 of tablespace 0

     

2017-06-05 16:46:03 2348 [Warning] InnoDB: Doublewrite does not have page_no = 0 of space: 0

     

2017-06-05 16:46:03 2348 [ERROR] InnoDB: space header page consists of zero bytes in data file C: \ xampp \ mysql \ data \ ibdata1

     

2017-06-05 16:46:03 2348 [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-06-05 16:46:03 2348 [ERROR] Plugin 'InnoDB' init function returned error.

     

2017-06-05 16:46:03 2348 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.

     

2017-06-05 16:46:03 2348 [Note] Plugin 'FEEDBACK' is disabled.

     

2017-06-05 16:46:03 2348 [ERROR] Unknown / unsupported storage engine: InnoDB

     

2017-06-05 16:46:03 2348 [ERROR] Aborting

Now try to give solution by deleting the file ibdata 1 and change the ports by 8080 but none of this works.

Someone who can help me?

    
asked by Laura Lopez Padilla 05.06.2017 в 23:48
source

1 answer

1

Apparently, the best option is to reinstall XAMPP. They have asked again how it was solved and this has been the final solution, reinstall. I leave a link to the post.

Problem with apache in XAMPP

    
answered by 09.10.2017 в 20:39