MySQL Forums
Forum List  »  Newbie

MySql Log File Error
Posted by: Macey Macintosh
Date: May 22, 2013 07:57AM

Hello! I'm a brand-new MySql user. Yesterday I started up wiki based of of my local server, and it worked beautifully (no errors). But today I tried to get it started up and I keep getting the infamous "Unexpected end of MySql... see log file?". I've tried everything the interwebs suggested, such as changing user permissions, restarting Apache and my computer, and I just tried to take a look at the log file to see what was up. It's repeating itself, but there seem to be two main errors:

3-05-21 16:02:43 2ac InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-05-21 16:02:43 2ac InnoDB: Recalculation of persistent statistics requested for table "my_wiki"."objectcache" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.


3-05-22 09:35:03 2876 [Note] Plugin 'FEDERATED' is disabled.
2013-05-22 09:35:03 52c 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-05-22 09:35:03 2876 [Note] InnoDB: The InnoDB memory heap is disabled
2013-05-22 09:35:03 2876 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-05-22 09:35:03 2876 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-05-22 09:35:03 2876 [Note] InnoDB: Not using CPU crc32 instructions
2013-05-22 09:35:03 2876 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-05-22 09:35:03 2876 [Note] InnoDB: Completed initialization of buffer pool
2013-05-22 09:35:03 2876 [Note] InnoDB: Highest supported file format is Barracuda.
2013-05-22 09:35:03 2876 [Note] InnoDB: The log sequence numbers 1600607 and 1600607 in ibdata files do not match the log sequence number 3862101 in the ib_logfiles!
2013-05-22 09:35:03 2876 [Note] InnoDB: Database was not shutdown normally!
2013-05-22 09:35:03 2876 [Note] InnoDB: Starting crash recovery.
2013-05-22 09:35:03 2876 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-05-22 09:35:03 2876 [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 my_wiki/user which uses space ID: 1 at filepath: .\my_wiki\user.ibd
InnoDB: Error: could not open single-table tablespace file .\my_wiki\user.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.

I'm not sure what program you can use to open an .ibd file (namely the user.ibd file), and when I tried to open it with jEdit the encoding was screwed up. I would really appreciate some help! I'm completely lost.

Thank you!

Options: ReplyQuote

Written By
MySql Log File Error
May 22, 2013 07:57AM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.