acicovic Posted August 17, 2015 Report Share Posted August 17, 2015 Hello there, Running Windows 7 x64 with UniServer latest version (11_8_0_ZeroXI), and update to MySQL 5.6.26. If I restart the computer without shutting down MySQL from UniController first, MySQL is not shut down gracefully (I assume this because I see no traces of shutting down in the log). Upon reboot, and when I will try to start the MySQL server, it will not start and I will get a log like that: Version: '5.6.26' socket: '' port: 3306 MySQL Community Server (GPL)2015-08-16 23:21:50 4376 [Note] Plugin 'FEDERATED' is disabled.2015-08-16 23:21:50 4376 [Note] InnoDB: Using atomics to ref count buffer pool pages2015-08-16 23:21:50 4376 [Note] InnoDB: The InnoDB memory heap is disabled2015-08-16 23:21:50 4376 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions2015-08-16 23:21:50 4376 [Note] InnoDB: Memory barrier is not used2015-08-16 23:21:50 4376 [Note] InnoDB: Compressed tables use zlib 1.2.32015-08-16 23:21:50 4376 [Note] InnoDB: Not using CPU crc32 instructions2015-08-16 23:21:50 4376 [Note] InnoDB: Initializing buffer pool, size = 16.0M2015-08-16 23:21:50 4376 [Note] InnoDB: Completed initialization of buffer pool2015-08-16 23:21:50 4376 [Note] InnoDB: Highest supported file format is Barracuda.2015-08-16 23:21:50 4376 [Note] InnoDB: The log sequence numbers 104865222 and 104865222 in ibdata files do not match the log sequence number 104865232 in the ib_logfiles!2015-08-16 23:21:50 4376 [Note] InnoDB: Database was not shutdown normally!2015-08-16 23:21:50 4376 [Note] InnoDB: Starting crash recovery.2015-08-16 23:21:50 4376 [Note] InnoDB: Reading tablespace information from the .ibd files...2015-08-16 23:21:52 4376 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_table_stats uses space ID: 1 at filepath: .\mysql\innodb_table_stats.ibd. Cannot open tablespace phpmyadmin/pma__bookmark which uses space ID: 1 at filepath: .\phpmyadmin\pma__bookmark.ibdInnoDB: Error: could not open single-table tablespace file .\phpmyadmin\pma__bookmark.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. Is this a known issue? is there a fix to this? Thanks! Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.