Page 1 of 1

[BUG] XAMPP 1.8.2-1 & 1.8.3-0 issues

PostPosted: 31. July 2013 05:35
by Altrea
In this thread we collect all issues with XAMPP for Windows 1.8.2-1 & 1.8.3-0 issues
To report a bug simply create a new forum thread

XAMPP 1.8.2-1



XAMPP 1.8.3



not a bug

MySQL cannot start after stopped (InnoDB crash recovery)

PostPosted: 21. August 2013 20:40
by Altrea
Bug Report
mysql_error.log wrote:{YYYY-mm-dd HH:ii:ss} 8012 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace {database name}/{database table name} uses space ID: {#} at filepath: .\{database name}\{database table name}.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: {#} at filepath: .\mysql\innodb_index_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.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.

Reproducible Testcase
None yet.
Reports say that this issue occurs after a MySQL restart, but i can't reproduce the issue yet.
Maybe this issue just occurs if XAMPP gets upgraded and not with fresh installations.
If someone can report a working reproducible testcase, let me know.

Affected XAMPP versions
All XAMPP versions containing MySQL 5.6.X

Solutions / Workarounds
  • using XAMPP 1.8.2-1 (MySQL 5.5.32)
  • deleting the \xampp\mysql\data\ibdata1 file (data loss of all InnoDB Databases !!!)


Re: [BUG] XAMPP 1.8.2-1 & 1.8.3 issues

PostPosted: 02. September 2013 10:03
by Beltran

Thanks for reporting it. It seems the 1.8.3 issue with MySQL database is only upgrading a database from a previous MySQL 5.5 version. We continue investigating it.

Re: [BUG] XAMPP 1.8.2-1 & 1.8.3-0 issues

PostPosted: 04. September 2013 12:58
by Beltran
Just a note, we can not reproduce this issue neither. It seems the user has copied a previous database (based on MySQL 5.5) and try to start it. It is recommended to run the "mysql_upgrade" command when you move a database from a previous MySQL major version.