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

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

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

Postby Altrea » 31. July 2013 05:35

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

confirmed

acknowledged

XAMPP 1.8.3

confirmed

acknowledged

not a bug
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: 8299
Joined: 17. August 2009 13:05
XAMPP version: several
Operating System: Windows 10 Pro x64

MySQL cannot start after stopped (InnoDB crash recovery)

Postby Altrea » 21. August 2013 20:40

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)
    or
  • deleting the \xampp\mysql\data\ibdata1 file (data loss of all InnoDB Databases !!!)

References
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: 8299
Joined: 17. August 2009 13:05
XAMPP version: several
Operating System: Windows 10 Pro x64

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

Postby Beltran » 02. September 2013 10:03

Hi,

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.
User avatar
Beltran
Power-User
 
Posts: 108
Joined: 22. March 2013 12:29
Operating System: Windows, Linux, OS X

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

Postby Beltran » 04. September 2013 12:58

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.
User avatar
Beltran
Power-User
 
Posts: 108
Joined: 22. March 2013 12:29
Operating System: Windows, Linux, OS X


Return to XAMPP for Windows

Who is online

Users browsing this forum: No registered users and 67 guests