MySQL startet nicht mehr seit Xampp Update

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

MySQL startet nicht mehr seit Xampp Update

Postby x16 » 26. March 2015 12:34

Ich habe die neuste Version von Xampp gestern installiert und auch angepasst, wie immer. Alles lief, auch nach mehreren Neustarts. Heute morgen aber startet MySQL plötzlich nicht mehr. Habe schon rausgefunden, dass es wohl an 2 Datenbanken liegt. Aber die Datenbanken können nicht defekt sein, da sie im alten Xampp laufen.

Hier das Logfile:

Code: Select all
2015-03-26 12:29:03 2252 [Note] Plugin 'FEDERATED' is disabled.
2015-03-26 12:29:03 11a0 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.
2015-03-26 12:29:03 2252 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-03-26 12:29:03 2252 [Note] InnoDB: The InnoDB memory heap is disabled
2015-03-26 12:29:03 2252 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-03-26 12:29:03 2252 [Note] InnoDB: Memory barrier is not used
2015-03-26 12:29:03 2252 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-03-26 12:29:03 2252 [Note] InnoDB: Not using CPU crc32 instructions
2015-03-26 12:29:03 2252 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-03-26 12:29:03 2252 [Note] InnoDB: Completed initialization of buffer pool
2015-03-26 12:29:04 2252 [Note] InnoDB: Highest supported file format is Barracuda.
2015-03-26 12:29:04 2252 [Note] InnoDB: The log sequence numbers 1665234 and 1665234 in ibdata files do not match the log sequence number 1665598 in the ib_logfiles!
2015-03-26 12:29:04 2252 [Note] InnoDB: Database was not shutdown normally!
2015-03-26 12:29:04 2252 [Note] InnoDB: Starting crash recovery.
2015-03-26 12:29:04 2252 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-03-26 12:29:04 2252 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace phpmyadmin/pma_usergroups uses space ID: 7 at filepath: .\phpmyadmin\pma_usergroups.ibd. Cannot open tablespace _pricats/daten which uses space ID: 7 at filepath: .\_pricats\daten.ibd
InnoDB: Error: could not open single-table tablespace file .\_pricats\daten.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.


Wenn ich das aktuelle MySQL Verzeichnis umbenenne und das MySQL aus der alten Xampp installaion in die neue kopiere läuft MySQL wieder. Scheint also irgendwas an der neuen Version zu sein. Wäre echt super, wenn jemand anhand des Logfiles etwas finden würde.
Danke.
x16
 
Posts: 13
Joined: 03. March 2011 15:40

Return to MariaDB - MySQL

Who is online

Users browsing this forum: No registered users and 2 guests