XAMPP – Blbne MySQL

11. 10. 2013 00:19:29

Zdravím,

Nějak mi začalo hafrovat mysql xampp mi vypisuje:

ERROR LOG

2013-10-11 00:17:30 4216  Plugin 'FEDERATED' is disabled.2013-10-11 00:17:30 15d0 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-10-11 00:17:30 4216  InnoDB: The InnoDB memory heap is disabled2013-10-11 00:17:30 4216  InnoDB: Mutexes and rw_locks use Windows interlocked functions2013-10-11 00:17:30 4216  InnoDB: Compressed tables use zlib 1.2.32013-10-11 00:17:30 4216  InnoDB: Not using CPU crc32 instructions2013-10-11 00:17:30 4216  InnoDB: Initializing buffer pool, size = 16.0M2013-10-11 00:17:30 4216  InnoDB: Completed initialization of buffer pool2013-10-11 00:17:30 4216  InnoDB: Highest supported file format is Barracuda.2013-10-11 00:17:30 4216  InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1645433 in the ib_logfiles!2013-10-11 00:17:30 4216  InnoDB: Database was not shutdown normally!2013-10-11 00:17:30 4216  InnoDB: Starting crash recovery.2013-10-11 00:17:30 4216  InnoDB: Reading tablespace information from the .ibd files...2013-10-11 00:17:30 4216  InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_index_stats uses space ID: 2 at filepath: .mysqlinnodb_index_stats.ibd. Cannot open tablespace test/table_web which uses space ID: 2 at filepath: .testtable_web.ibdInnoDB: Error: could not open single-table tablespace file .testtable_web.ibdInnoDB: We do not continue the crash recovery, because the table may becomeInnoDB: 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 cannotInnoDB: 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 normalInnoDB: crash recovery and ignore that table.InnoDB: 3) If the file system or the disk is broken, and you cannot removeInnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnfInnoDB: and force InnoDB to continue crash recovery here.

Port 3306 je volný

Apache se startlo v pohodě.

Vyřešeno, jedna stará DB mi začala hafrovat - už nepotřebna :D

11. 10. 2013 00:19:29