MYSQL stops working

Alles, was MariaDB und MySQL betrifft, kann hier besprochen werden.

MYSQL stops working

Postby palebluedot » 27. August 2013 21:28

I installed XAMPP v1.8.3 and everything worked perfectly—Apace and MYSQL via the control panel.
Then today MYSQL will not start up this is the error message and log that I receive:

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

Log file:
2013-08-27 13:26:55 4344 [Note] Plugin 'FEDERATED' is disabled.
2013-08-27 13:26:55 c08 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-08-27 13:26:55 4344 [Note] InnoDB: The InnoDB memory heap is disabled
2013-08-27 13:26:55 4344 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-08-27 13:26:55 4344 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-08-27 13:26:55 4344 [Note] InnoDB: Not using CPU crc32 instructions
2013-08-27 13:26:55 4344 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-08-27 13:26:55 4344 [Note] InnoDB: Completed initialization of buffer pool
2013-08-27 13:26:55 4344 [Note] InnoDB: Highest supported file format is Barracuda.
2013-08-27 13:26:55 4344 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1631139 in the ib_logfiles!
2013-08-27 13:26:55 4344 [Note] InnoDB: Database was not shutdown normally!
2013-08-27 13:26:55 4344 [Note] InnoDB: Starting crash recovery.
2013-08-27 13:26:55 4344 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-08-27 13:26:55 4344 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace dvd/dvd@0020listings uses space ID: 4 at filepath: .\dvd\dvd@0020listings.ibd. Cannot open tablespace mysql/slave_master_info which uses space ID: 4 at filepath: .\mysql\slave_master_info.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\slave_master_info.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.

Any help resolving this issue will be appreciated.
Posts: 3
Joined: 27. August 2013 21:19
Operating System: Windows 7

Re: MYSQL stops working

Postby Altrea » 27. August 2013 21:31

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

It's like porn for programmers 8)
User avatar
AF Moderator
Posts: 9063
Joined: 17. August 2009 13:05
XAMPP version: several
Operating System: Windows 10 Pro x64

Re: MYSQL stops working

Postby palebluedot » 27. August 2013 21:44

Thanks for the speedy reply!
Posts: 3
Joined: 27. August 2013 21:19
Operating System: Windows 7

Return to MariaDB - MySQL

Who is online

Users browsing this forum: No registered users and 2 guests