title: XAMPP - Error: MySQL shutdown unexpectedly
body: <p>I have reinstalled XAMPP for some reason and MySQL is not working, giving the following error in the console:</p>
  
  <pre><code>01:56:03  [mysql]   Error: MySQL shutdown unexpectedly.
  01:56:03  [mysql]   This may be due to a blocked port, missing dependencies, 
  01:56:03  [mysql]   improper privileges, a crash, or a shutdown by another method.
  01:56:03  [mysql]   Check the "/xampp/mysql/data/mysql_error.log" file
  01:56:03  [mysql]   and the Windows Event Viewer for more clues
  </code></pre>
  
  <p>When checking the "/xampp/mysql/data/mysql_error.log" file I get:</p>
  
  <pre><code>130302  1:48:06  InnoDB: Waiting for the background threads to start
  130302  1:48:07 InnoDB: 1.1.8 started; log sequence number 1600324627
  130302  1:48:07 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
  130302  1:48:07 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
  130302  1:48:07 [Note] Server socket created on IP: '0.0.0.0'.
  130302  1:51:12 [Note] Plugin 'FEDERATED' is disabled.
  130302  1:51:12 InnoDB: The InnoDB memory heap is disabled
  130302  1:51:12 InnoDB: Mutexes and rw_locks use Windows interlocked functions
  130302  1:51:12 InnoDB: Compressed tables use zlib 1.2.3
  130302  1:51:12 InnoDB: Initializing buffer pool, size = 16.0M
  130302  1:51:12 InnoDB: Completed initialization of buffer pool
  130302  1:51:12 InnoDB: highest supported file format is Barracuda.
  InnoDB: The log sequence number in ibdata files does not match
  InnoDB: the log sequence number in the ib_logfiles!
  130302  1:51:12  InnoDB: Database was not shut down normally!
  InnoDB: Starting crash recovery.
  InnoDB: Reading tablespace information from the .ibd files...
  InnoDB: Restoring possible half-written data pages from the doublewrite
  InnoDB: buffer...
  130302  1:51:13  InnoDB: Waiting for the background threads to start
  130302  1:51:14 InnoDB: 1.1.8 started; log sequence number 1600324627
  130302  1:51:14 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
  130302  1:51:14 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
  130302  1:51:14 [Note] Server socket created on IP: '0.0.0.0'.
  130302  1:56:01 [Note] Plugin 'FEDERATED' is disabled.
  130302  1:56:01 InnoDB: The InnoDB memory heap is disabled
  130302  1:56:01 InnoDB: Mutexes and rw_locks use Windows interlocked functions
  130302  1:56:01 InnoDB: Compressed tables use zlib 1.2.3
  130302  1:56:01 InnoDB: Initializing buffer pool, size = 16.0M
  130302  1:56:01 InnoDB: Completed initialization of buffer pool
  130302  1:56:01 InnoDB: highest supported file format is Barracuda.
  InnoDB: The log sequence number in ibdata files does not match
  InnoDB: the log sequence number in the ib_logfiles!
  130302  1:56:01  InnoDB: Database was not shut down normally!
  InnoDB: Starting crash recovery.
  InnoDB: Reading tablespace information from the .ibd files...
  InnoDB: Restoring possible half-written data pages from the doublewrite
  InnoDB: buffer...
  130302  1:56:02  InnoDB: Waiting for the background threads to start
  130302  1:56:03 InnoDB: 1.1.8 started; log sequence number 1600324627
  130302  1:56:03 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
  130302  1:56:03 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
  130302  1:56:03 [Note] Server socket created on IP: '0.0.0.0'.
  </code></pre>
  
  <p>That is just a part of the log, the full one is a bit too big.</p>
  
  <p>Help?</p>