MySQL Will not start - Logs posted

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

MySQL Will not start - Logs posted

Postby jmdossetti » 06. December 2013 01:01

Hello - Hoping someone can help me with this who doesn't mind translating some of the more technical language for a non-developer. XAMPP was running for several days and seemed fine. I shut down, now it will not start. Apache started fine, but I get the following error for MySQL:

3:19:17 PM [mysql] Error: MySQL shutdown unexpectedly.
3:19:17 PM [mysql] This may be due to a blocked port, missing dependencies,
3:19:17 PM [mysql] improper privileges, a crash, or a shutdown by another method.
3:19:17 PM [mysql] Press the Logs button to view error logs and check
3:19:17 PM [mysql] the Windows Event Viewer for more clues
3:19:17 PM [mysql] If you need more help, copy and post this
3:19:17 PM [mysql] entire log window on the forums

I cannot seem to find anything running on the port. I don't know what "missing dependencies: refers to. Also not sure how I would check privileges, but since it was running fine yesterday and nothing has changed, I don't think that would be the issue.

I have seen this issue of not starting referenced on the forum in other places - Here for example -> http://community.apachefriends.org/f/viewtopic.php?f=16&t=66746#p230644, I read through this topic, but could not determine if my problem was similar and also even if it was, I did not understand the instructions on the fix or work around. I see in the log that it said database was not shut down normally. I hit stop and closed XAMPP - Is there some other way to shut down?

Here is my log file. Thanks in advance for any assistance.

2013-12-02 13:56:30 9432 [Note] Plugin 'FEDERATED' is disabled.
2013-12-02 13:56:30 25b8 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.
2013-12-02 13:56:30 9432 [Note] InnoDB: The InnoDB memory heap is disabled
2013-12-02 13:56:30 9432 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-12-02 13:56:30 9432 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-12-02 13:56:30 9432 [Note] InnoDB: Not using CPU crc32 instructions
2013-12-02 13:56:30 9432 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-12-02 13:56:30 9432 [Note] InnoDB: Completed initialization of buffer pool
2013-12-02 13:56:30 9432 [Note] InnoDB: The first specified data file C:\xampp\mysql\data\ibdata1 did not exist: a new database to be created!
2013-12-02 13:56:30 9432 [Note] InnoDB: Setting file C:\xampp\mysql\data\ibdata1 size to 10 MB
2013-12-02 13:56:30 9432 [Note] InnoDB: Database physically writes the file full: wait...
2013-12-02 13:56:31 9432 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile101 size to 5 MB
2013-12-02 13:56:31 9432 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile1 size to 5 MB
2013-12-02 13:56:32 9432 [Note] InnoDB: Renaming log file C:\xampp\mysql\data\ib_logfile101 to C:\xampp\mysql\data\ib_logfile0
2013-12-02 13:56:32 9432 [Warning] InnoDB: New log files created, LSN=45781
2013-12-02 13:56:32 9432 [Note] InnoDB: Doublewrite buffer not found: creating new
2013-12-02 13:56:32 9432 [Note] InnoDB: Doublewrite buffer created
2013-12-02 13:56:33 9432 [Note] InnoDB: 128 rollback segment(s) are active.
2013-12-02 13:56:33 9432 [Warning] InnoDB: Creating foreign key constraint system tables.
2013-12-02 13:56:33 9432 [Note] InnoDB: Foreign key constraint system tables created
2013-12-02 13:56:33 9432 [Note] InnoDB: Creating tablespace and datafile system tables.
2013-12-02 13:56:33 9432 [Note] InnoDB: Tablespace and datafile system tables created.
2013-12-02 13:56:33 9432 [Note] InnoDB: Waiting for purge to start
2013-12-02 13:56:33 9432 [Note] InnoDB: 5.6.11 started; log sequence number 0
2013-12-02 13:56:33 9432 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: 9bb142cf-5b9c-11e3-983e-6036ddce713c.
2013-12-02 13:56:33 9432 [Note] Server hostname (bind-address): '*'; port: 3306
2013-12-02 13:56:33 9432 [Note] IPv6 is available.
2013-12-02 13:56:33 9432 [Note] - '::' resolves to '::';
2013-12-02 13:56:33 9432 [Note] Server socket created on IP: '::'.
2013-12-05 14:43:36 9504 [Note] Plugin 'FEDERATED' is disabled.
2013-12-05 14:43:36 1ef0 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.
2013-12-05 14:43:36 9504 [Note] InnoDB: The InnoDB memory heap is disabled
2013-12-05 14:43:36 9504 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-12-05 14:43:36 9504 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-12-05 14:43:36 9504 [Note] InnoDB: Not using CPU crc32 instructions
2013-12-05 14:43:36 9504 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-12-05 14:43:36 9504 [Note] InnoDB: Completed initialization of buffer pool
2013-12-05 14:43:36 9504 [Note] InnoDB: Highest supported file format is Barracuda.
2013-12-05 14:43:36 9504 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2783200 in the ib_logfiles!
2013-12-05 14:43:36 9504 [Note] InnoDB: Database was not shutdown normally!
2013-12-05 14:43:36 9504 [Note] InnoDB: Starting crash recovery.
2013-12-05 14:43:36 9504 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-12-05 14:43:36 9504 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace wordpress/wp_terms which uses space ID: 3 at filepath: .\wordpress\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\wordpress\wp_terms.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.
2013-12-05 14:54:13 6624 [Note] Plugin 'FEDERATED' is disabled.
2013-12-05 14:54:13 19e4 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.
2013-12-05 14:54:13 6624 [Note] InnoDB: The InnoDB memory heap is disabled
2013-12-05 14:54:13 6624 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-12-05 14:54:13 6624 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-12-05 14:54:13 6624 [Note] InnoDB: Not using CPU crc32 instructions
2013-12-05 14:54:13 6624 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-12-05 14:54:13 6624 [Note] InnoDB: Completed initialization of buffer pool
2013-12-05 14:54:13 6624 [Note] InnoDB: Highest supported file format is Barracuda.
2013-12-05 14:54:14 6624 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2783200 in the ib_logfiles!
2013-12-05 14:54:14 6624 [Note] InnoDB: Database was not shutdown normally!
2013-12-05 14:54:14 6624 [Note] InnoDB: Starting crash recovery.
2013-12-05 14:54:14 6624 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-12-05 14:54:14 6624 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace wordpress/wp_terms which uses space ID: 3 at filepath: .\wordpress\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\wordpress\wp_terms.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.
2013-12-05 14:54:46 6788 [Note] Plugin 'FEDERATED' is disabled.
2013-12-05 14:54:46 1a88 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.
2013-12-05 14:54:46 6788 [Note] InnoDB: The InnoDB memory heap is disabled
2013-12-05 14:54:46 6788 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-12-05 14:54:46 6788 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-12-05 14:54:46 6788 [Note] InnoDB: Not using CPU crc32 instructions
2013-12-05 14:54:46 6788 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-12-05 14:54:46 6788 [Note] InnoDB: Completed initialization of buffer pool
2013-12-05 14:54:46 6788 [Note] InnoDB: Highest supported file format is Barracuda.
2013-12-05 14:54:46 6788 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2783200 in the ib_logfiles!
2013-12-05 14:54:46 6788 [Note] InnoDB: Database was not shutdown normally!
2013-12-05 14:54:46 6788 [Note] InnoDB: Starting crash recovery.
2013-12-05 14:54:46 6788 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-12-05 14:54:46 6788 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace wordpress/wp_terms which uses space ID: 3 at filepath: .\wordpress\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\wordpress\wp_terms.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.
jmdossetti
 
Posts: 2
Joined: 06. December 2013 00:11
XAMPP Version: 1.8.3-3
Operating System: Windows 8

Re: MySQL Will not start - Logs posted

Postby Altrea » 06. December 2013 05:30

Hi,

This way please: viewtopic.php?f=16&t=66746#p230644

best wishes,
Altrea
We don't provide any support via personal channels like PM, email, Skype, TeamViewer!

It's like porn for programmers 8)
User avatar
Altrea
AF Moderator
 
Posts: 6545
Joined: 17. August 2009 13:05
XAMPP Version: 5.5.19
Operating System: W7Ux64

Re: MySQL Will not start - Logs posted

Postby jmdossetti » 06. December 2013 18:36

Thanks Altrea - I appreciate the quick response. I had read that post several times, but couldn't make heads or tails of it. (I'm not a developer, but a designer trying to learn this stuff)

I gave the post one more read and picked the solution that I sort of understood how to do and seemed least complicated (deleting the \xampp\mysql\data\ibdata1 file (data loss of all InnoDB Databases !!!))

Somehow, it worked!! Fingers crossed that I can continue to start MySQL after today.

Thanks again,
Jen
jmdossetti
 
Posts: 2
Joined: 06. December 2013 00:11
XAMPP Version: 1.8.3-3
Operating System: Windows 8

Re: MySQL Will not start - Logs posted

Postby Altrea » 06. December 2013 18:41

This is just a quick fix. The problem can reoccure.

i would recommend you to use the current XAMPP version 1.8.3-2. The changelog reports that the MySQL issue should be solved in the current version.
Or you could use the XAMPP version 1.8.2-3. The containing MySQL minor version is not that susceptible for that issue.
We don't provide any support via personal channels like PM, email, Skype, TeamViewer!

It's like porn for programmers 8)
User avatar
Altrea
AF Moderator
 
Posts: 6545
Joined: 17. August 2009 13:05
XAMPP Version: 5.5.19
Operating System: W7Ux64


Return to XAMPP for Windows

Who is online

Users browsing this forum: No registered users and 64 guests