Error starting MySQL, need help with log report please!

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

Error starting MySQL, need help with log report please!

Postby hconroy » 27. January 2014 19:50

Hi,

I'm a newbie using XAMPP. My setup was working fine a few days ago, but today when I opened the XAMPP Control Panel, Apache started as normal, but MySQL won't. Here's the error log report:

2014-01-27 18:27:19 1924 [Note] Plugin 'FEDERATED' is disabled.
2014-01-27 18:27:19 1158 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.
2014-01-27 18:27:19 1924 [Note] InnoDB: The InnoDB memory heap is disabled
2014-01-27 18:27:19 1924 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-01-27 18:27:19 1924 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-01-27 18:27:19 1924 [Note] InnoDB: Not using CPU crc32 instructions
2014-01-27 18:27:19 1924 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-01-27 18:27:19 1924 [Note] InnoDB: Completed initialization of buffer pool
2014-01-27 18:27:19 1924 [Note] InnoDB: Highest supported file format is Barracuda.
2014-01-27 18:27:19 1924 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1610495 in the ib_logfiles!
2014-01-27 18:27:19 1924 [Note] InnoDB: Database was not shutdown normally!
2014-01-27 18:27:19 1924 [Note] InnoDB: Starting crash recovery.
2014-01-27 18:27:19 1924 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-01-27 18:27:19 1924 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace cs5017/users uses space ID: 1 at filepath: .\cs5017\users.ibd. Cannot open tablespace mysql/innodb_table_stats which uses space ID: 1 at filepath: .\mysql\innodb_table_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_table_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.

Does anyone know what my problem is?

Thanks for help!
hconroy
 
Posts: 2
Joined: 27. January 2014 19:35
Operating System: Windows 7

Re: Error starting MySQL, need help with log report please!

Postby Altrea » 28. January 2014 00:45

Hi hconroy,

This way please: viewtopic.php?f=16&t=66746&p=230644#p230644

best wishes,
Altrea
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: 11926
Joined: 17. August 2009 13:05
XAMPP version: several
Operating System: Windows 11 Pro x64

Re: Error starting MySQL, need help with log report please!

Postby hconroy » 28. January 2014 01:10

Thank you!
hconroy
 
Posts: 2
Joined: 27. January 2014 19:35
Operating System: Windows 7


Return to XAMPP for Windows

Who is online

Users browsing this forum: No registered users and 132 guests