follow us on google+ follow us feedburner

FORUM
We will close this forum soon. Please, now use Stack Overflow. Don't forget to add the tag "easyphp" to your post.

You can follow your activity on Stack Overflow with the Stack Exchange Android App. An iPhone version is coming...

One more thing. EasyPHP is on GitHub. You will find the repositories at this address : https://github.com/easyphp. If you want to report a bug, please use the GitHub issue management system of each repository.

Unexpexted end of MySql (Can`t start)



Posted by: John
May 25, 2013 11:58AM
[i.imgur.com]

2013-05-25 12:53:49 3108 [Note] Plugin 'FEDERATED' is disabled.
2013-05-25 12:53:49 1378 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-25 12:53:49 3108 [Note] InnoDB: The InnoDB memory heap is disabled
2013-05-25 12:53:49 3108 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-05-25 12:53:49 3108 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-05-25 12:53:49 3108 [Note] InnoDB: Not using CPU crc32 instructions
2013-05-25 12:53:49 3108 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-05-25 12:53:49 3108 [Note] InnoDB: Completed initialization of buffer pool
2013-05-25 12:53:49 3108 [Note] InnoDB: Highest supported file format is Barracuda.
2013-05-25 12:53:49 3108 [Note] InnoDB: The log sequence numbers 3485074 and 3485074 in ibdata files do not match the log sequence number 3955152 in the ib_logfiles!
2013-05-25 12:53:49 3108 [Note] InnoDB: Database was not shutdown normally!
2013-05-25 12:53:49 3108 [Note] InnoDB: Starting crash recovery.
2013-05-25 12:53:49 3108 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-05-25 12:53:49 3108 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace antanas/wp_usermeta uses space ID: 2 at filepath: .\antanas\wp_usermeta.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 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.
Options: ReplyQuote
Posted by: cgtb
June 02, 2013 04:16PM
Same issue. the only solution I have is to reinstall EasyPHP, and this error occurs again each time I restart my computer.
Any hints?
Options: ReplyQuote
Posted by: mitshu
June 03, 2013 07:10PM
I have the same issue too, i have no idea how to resolve it, please help!
Options: ReplyQuote
June 05, 2013 09:21AM
Same thing is here - on 2 different computers (win7[x86] & win 8[x64])
It deleted all my databases... How can we recover thm after the new installation?
[sorry guys, but for now I'm using XAMPP even that I prefer to use easyPHP]
Options: ReplyQuote
August 01, 2013 09:47PM
"For Windows 7 try VC++ 2010 or DLL MSVCR110.DLL to install in Windows \ System32"
I do this but the problem continue...

(win 7 - 64)

The log file:

2013-08-01 16:24:48 3500 [Note] Plugin 'FEDERATED' is disabled.
2013-08-01 16:24:48 f0c 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-08-01 16:24:48 3500 [Note] InnoDB: The InnoDB memory heap is disabled
2013-08-01 16:24:48 3500 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-08-01 16:24:48 3500 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-08-01 16:24:48 3500 [Note] InnoDB: Not using CPU crc32 instructions
2013-08-01 16:24:48 3500 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-08-01 16:24:48 3500 [Note] InnoDB: Completed initialization of buffer pool
2013-08-01 16:24:48 3500 [Note] InnoDB: The first specified data file .\ibdata1 did not exist: a new database to be created!
2013-08-01 16:24:48 3500 [Note] InnoDB: Setting file .\ibdata1 size to 12 MB
2013-08-01 16:24:48 3500 [Note] InnoDB: Database physically writes the file full: wait...
2013-08-01 16:24:48 3500 [Note] InnoDB: Setting log file .\ib_logfile101 size to 5 MB
2013-08-01 16:24:49 3500 [Note] InnoDB: Setting log file .\ib_logfile1 size to 5 MB
2013-08-01 16:24:49 3500 [Note] InnoDB: Renaming log file .\ib_logfile101 to .\ib_logfile0
2013-08-01 16:24:49 3500 [Warning] InnoDB: New log files created, LSN=45781
2013-08-01 16:24:49 3500 [Note] InnoDB: Doublewrite buffer not found: creating new
2013-08-01 16:24:49 3500 [Note] InnoDB: Doublewrite buffer created
2013-08-01 16:24:49 3500 [Note] InnoDB: 128 rollback segment(s) are active.
2013-08-01 16:24:49 3500 [Warning] InnoDB: Creating foreign key constraint system tables.
2013-08-01 16:24:49 3500 [Note] InnoDB: Foreign key constraint system tables created
2013-08-01 16:24:49 3500 [Note] InnoDB: Creating tablespace and datafile system tables.
2013-08-01 16:24:49 3500 [Note] InnoDB: Tablespace and datafile system tables created.
2013-08-01 16:24:49 3500 [Note] InnoDB: Waiting for purge to start
2013-08-01 16:24:49 3500 [Note] InnoDB: 5.6.12 started; log sequence number 0
2013-08-01 16:24:49 3500 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
2013-08-01 16:24:49 3500 [Note] - '127.0.0.1' resolves to '127.0.0.1';
2013-08-01 16:24:49 3500 [Note] Server socket created on IP: '127.0.0.1'.
2013-08-01 16:24:49 3500 [Warning] InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See [dev.mysql.com] for how you can resolve the problem.
2013-08-01 16:24:49 3500 [Warning] Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.
2013-08-01 16:24:49 3500 [Warning] InnoDB: Cannot open table mysql/slave_worker_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See [dev.mysql.com] for how you can resolve the problem.
2013-08-01 16:24:49 3500 [Warning] InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See [dev.mysql.com] for how you can resolve the problem.
2013-08-01 16:24:49 3500 [Warning] Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.
2013-08-01 16:24:49 3500 [Note] Event Scheduler: Loaded 0 events
2013-08-01 16:24:49 3500 [Note] C:\PROGRA~2\EASYPH~1.1VC\binaries\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.12-log' socket: '' port: 3306 MySQL Community Server (GPL)
2013-08-01 16:34:07 3408 [Note] Plugin 'FEDERATED' is disabled.
2013-08-01 16:34:07 d54 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-08-01 16:34:07 3408 [Note] InnoDB: The InnoDB memory heap is disabled
2013-08-01 16:34:07 3408 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-08-01 16:34:07 3408 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-08-01 16:34:07 3408 [Note] InnoDB: Not using CPU crc32 instructions
2013-08-01 16:34:07 3408 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-08-01 16:34:07 3408 [Note] InnoDB: Completed initialization of buffer pool
2013-08-01 16:34:07 3408 [Note] InnoDB: Highest supported file format is Barracuda.
2013-08-01 16:34:08 3408 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1600607 in the ib_logfiles!
2013-08-01 16:34:08 3408 [Note] InnoDB: Database was not shutdown normally!
2013-08-01 16:34:08 3408 [Note] InnoDB: Starting crash recovery.
2013-08-01 16:34:08 3408 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-08-01 16:34:08 3408 [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 teste/categories which uses space ID: 1 at filepath: .\teste\categories.ibd
InnoDB: Error: could not open single-table tablespace file .\teste\categories.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.
2013-08-01 16:34:16 3860 [Note] Plugin 'FEDERATED' is disabled.
2013-08-01 16:34:16 f18 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-08-01 16:34:16 3860 [Note] InnoDB: The InnoDB memory heap is disabled
2013-08-01 16:34:16 3860 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-08-01 16:34:16 3860 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-08-01 16:34:16 3860 [Note] InnoDB: Not using CPU crc32 instructions
2013-08-01 16:34:16 3860 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-08-01 16:34:16 3860 [Note] InnoDB: Completed initialization of buffer pool
2013-08-01 16:34:16 3860 [Note] InnoDB: Highest supported file format is Barracuda.
2013-08-01 16:34:16 3860 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1600607 in the ib_logfiles!
2013-08-01 16:34:16 3860 [Note] InnoDB: Database was not shutdown normally!
2013-08-01 16:34:16 3860 [Note] InnoDB: Starting crash recovery.
2013-08-01 16:34:16 3860 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-08-01 16:34:16 3860 [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 teste/categories which uses space ID: 1 at filepath: .\teste\categories.ibd
InnoDB: Error: could not open single-table tablespace file .\teste\categories.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.
2013-08-01 16:34:33 4064 [Note] Plugin 'FEDERATED' is disabled.
2013-08-01 16:34:33 fe4 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-08-01 16:34:33 4064 [Note] InnoDB: The InnoDB memory heap is disabled
2013-08-01 16:34:33 4064 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-08-01 16:34:33 4064 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-08-01 16:34:33 4064 [Note] InnoDB: Not using CPU crc32 instructions
2013-08-01 16:34:33 4064 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-08-01 16:34:33 4064 [Note] InnoDB: Completed initialization of buffer pool
2013-08-01 16:34:33 4064 [Note] InnoDB: Highest supported file format is Barracuda.
2013-08-01 16:34:33 4064 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1600607 in the ib_logfiles!
2013-08-01 16:34:33 4064 [Note] InnoDB: Database was not shutdown normally!
2013-08-01 16:34:33 4064 [Note] InnoDB: Starting crash recovery.
2013-08-01 16:34:33 4064 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-08-01 16:34:33 4064 [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 teste/categories which uses space ID: 1 at filepath: .\teste\categories.ibd
InnoDB: Error: could not open single-table tablespace file .\teste\categories.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.
2013-08-01 16:35:43 380 [Note] Plugin 'FEDERATED' is disabled.
2013-08-01 16:35:43 3d8 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-08-01 16:35:43 380 [Note] InnoDB: The InnoDB memory heap is disabled
2013-08-01 16:35:43 380 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-08-01 16:35:43 380 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-08-01 16:35:43 380 [Note] InnoDB: Not using CPU crc32 instructions
2013-08-01 16:35:43 380 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-08-01 16:35:43 380 [Note] InnoDB: Completed initialization of buffer pool
2013-08-01 16:35:43 380 [Note] InnoDB: Highest supported file format is Barracuda.
2013-08-01 16:35:43 380 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1600607 in the ib_logfiles!
2013-08-01 16:35:43 380 [Note] InnoDB: Database was not shutdown normally!
2013-08-01 16:35:43 380 [Note] InnoDB: Starting crash recovery.
2013-08-01 16:35:43 380 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-08-01 16:35:43 380 [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 teste/categories which uses space ID: 1 at filepath: .\teste\categories.ibd
InnoDB: Error: could not open single-table tablespace file .\teste\categories.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.
2013-08-01 16:35:48 2812 [Note] Plugin 'FEDERATED' is disabled.
2013-08-01 16:35:48 af8 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-08-01 16:35:48 2812 [Note] InnoDB: The InnoDB memory heap is disabled
2013-08-01 16:35:48 2812 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-08-01 16:35:48 2812 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-08-01 16:35:48 2812 [Note] InnoDB: Not using CPU crc32 instructions
2013-08-01 16:35:48 2812 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-08-01 16:35:48 2812 [Note] InnoDB: Completed initialization of buffer pool
2013-08-01 16:35:48 2812 [Note] InnoDB: Highest supported file format is Barracuda.
2013-08-01 16:35:48 2812 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1600607 in the ib_logfiles!
2013-08-01 16:35:48 2812 [Note] InnoDB: Database was not shutdown normally!
2013-08-01 16:35:48 2812 [Note] InnoDB: Starting crash recovery.
2013-08-01 16:35:48 2812 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-08-01 16:35:48 2812 [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 teste/categories which uses space ID: 1 at filepath: .\teste\categories.ibd
InnoDB: Error: could not open single-table tablespace file .\teste\categories.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.
2013-08-01 16:35:55 820 [Note] Plugin 'FEDERATED' is disabled.
2013-08-01 16:35:55 444 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-08-01 16:35:55 820 [Note] InnoDB: The InnoDB memory heap is disabled
2013-08-01 16:35:55 820 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-08-01 16:35:55 820 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-08-01 16:35:55 820 [Note] InnoDB: Not using CPU crc32 instructions
2013-08-01 16:35:55 820 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-08-01 16:35:55 820 [Note] InnoDB: Completed initialization of buffer pool
2013-08-01 16:35:55 820 [Note] InnoDB: Highest supported file format is Barracuda.
2013-08-01 16:35:55 820 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1600607 in the ib_logfiles!
2013-08-01 16:35:55 820 [Note] InnoDB: Database was not shutdown normally!
2013-08-01 16:35:55 820 [Note] InnoDB: Starting crash recovery.
2013-08-01 16:35:55 820 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-08-01 16:35:55 820 [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 teste/categories which uses space ID: 1 at filepath: .\teste\categories.ibd
InnoDB: Error: could not open single-table tablespace file .\teste\categories.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.
2013-08-01 16:36:03 3520 [Note] Plugin 'FEDERATED' is disabled.
2013-08-01 16:36:03 dc4 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-08-01 16:36:03 3520 [Note] InnoDB: The InnoDB memory heap is disabled
2013-08-01 16:36:03 3520 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-08-01 16:36:03 3520 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-08-01 16:36:03 3520 [Note] InnoDB: Not using CPU crc32 instructions
2013-08-01 16:36:03 3520 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-08-01 16:36:03 3520 [Note] InnoDB: Completed initialization of buffer pool
2013-08-01 16:36:03 3520 [Note] InnoDB: Highest supported file format is Barracuda.
2013-08-01 16:36:03 3520 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1600607 in the ib_logfiles!
2013-08-01 16:36:03 3520 [Note] InnoDB: Database was not shutdown normally!
2013-08-01 16:36:04 3520 [Note] InnoDB: Starting crash recovery.
2013-08-01 16:36:04 3520 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-08-01 16:36:04 3520 [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 teste/categories which uses space ID: 1 at filepath: .\teste\categories.ibd
InnoDB: Error: could not open single-table tablespace file .\teste\categories.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.
2013-08-01 16:36:20 3440 [Note] Plugin 'FEDERATED' is disabled.
2013-08-01 16:36:20 d64 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-08-01 16:36:20 3440 [Note] InnoDB: The InnoDB memory heap is disabled
2013-08-01 16:36:20 3440 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-08-01 16:36:20 3440 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-08-01 16:36:20 3440 [Note] InnoDB: Not using CPU crc32 instructions
2013-08-01 16:36:20 3440 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-08-01 16:36:20 3440 [Note] InnoDB: Completed initialization of buffer pool
2013-08-01 16:36:20 3440 [Note] InnoDB: Highest supported file format is Barracuda.
2013-08-01 16:36:20 3440 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1600607 in the ib_logfiles!
2013-08-01 16:36:20 3440 [Note] InnoDB: Database was not shutdown normally!
2013-08-01 16:36:20 3440 [Note] InnoDB: Starting crash recovery.
2013-08-01 16:36:20 3440 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-08-01 16:36:20 3440 [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 teste/categories which uses space ID: 1 at filepath: .\teste\categories.ibd
InnoDB: Error: could not open single-table tablespace file .\teste\categories.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.
Options: ReplyQuote
Posted by: Maksii
June 05, 2013 11:53AM
Same problem here! Help!
The permission tip doesnt work, it's something else..
Options: ReplyQuote
Posted by: Yohann
June 08, 2013 06:42PM
Try to add the following line in the file my.ini :

innodb_force_recovery = 1

Hope this helps
Options: ReplyQuote
Posted by: TR@SOE
June 12, 2013 11:27AM
I have posted my solution earlier:

[www.easyphp.org]
Options: ReplyQuote
Posted by: Kyle
June 13, 2013 09:05AM
TR@SOE your solution seems to get MYSQL running, but even when I go to access MySQL Administration : PhpMyAdmin 3.5.8.1 I get the following error:

#2002 - No connection could be made because the target machine actively refused it.

The server is not responding (or the local server's socket is not correctly configured).
Options: ReplyQuote
Posted by: TR@SOE
July 04, 2013 04:33AM
Thanks for sharing your experience.

PHPMYAdmin can't connect to MySQL could be some cookie/cache problem when it stored a PID for MySQL daemon but that PID will be invalid after a restart of MySQL anyway. Normally, after browser restart, or desktop reboot, it should at least solve this problem.

If it consists, two possible suggestions:

1. Use another lighter admin GUI to admin your MySQL or just use plain mysql console;
2. Try change your PHPMyAdmin config from "cookie" to "config" (in most cases it will cause your unable to login into PHPMyAdmin unless your root password is empty or you have made correct server config), then change it back.

See if this works.
Options: ReplyQuote
Posted by: cipher
June 20, 2013 07:38AM
I have the same problem. Each time i restart my computer, and start EasyPHP,"Unexpected End of MySqL....See log file?" occurs! if i use

innodb_force_recovery = 1

Then everything on my database is deleted + when i try to drop the database mysqld stops running. I think it's the bug in DevServer.

Any help / or patch to fix the bug will be good
Options: ReplyQuote
Posted by: Naarciss
June 24, 2013 02:55PM
cipher Wrote:
-------------------------------------------------------
> I have the same problem. Each time i restart my
> computer, and start EasyPHP,"Unexpected End of
> MySqL....See log file?" occurs! if i use
>
> innodb_force_recovery = 1
>
> Then everything on my database is deleted + when i
> try to drop the database mysqld stops running. I
> think it's the bug in DevServer.
>
> Any help / or patch to fix the bug will be good

Did the same and after WP migrate i get error that my DB is broken... Switched to Xampp till EP13 get repaired :(
Options: ReplyQuote
Posted by: Thierry53
July 08, 2013 05:03PM
out of curiosity ...

Do you have the Microsoft redistributable Visual C + + 2008 installed on your computer?

this set installs some dll used by EasyPhp ...
For Windows 7 try VC++ 2010 or DLL MSVCR110.DLL to install in Windows \ System32
Options: ReplyQuote
August 01, 2013 09:45PM
Same problem

The log file:

2013-08-01 16:24:48 3500 [Note] Plugin 'FEDERATED' is disabled.
2013-08-01 16:24:48 f0c 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-08-01 16:24:48 3500 [Note] InnoDB: The InnoDB memory heap is disabled
2013-08-01 16:24:48 3500 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-08-01 16:24:48 3500 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-08-01 16:24:48 3500 [Note] InnoDB: Not using CPU crc32 instructions
2013-08-01 16:24:48 3500 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-08-01 16:24:48 3500 [Note] InnoDB: Completed initialization of buffer pool
2013-08-01 16:24:48 3500 [Note] InnoDB: The first specified data file .\ibdata1 did not exist: a new database to be created!
2013-08-01 16:24:48 3500 [Note] InnoDB: Setting file .\ibdata1 size to 12 MB
2013-08-01 16:24:48 3500 [Note] InnoDB: Database physically writes the file full: wait...
2013-08-01 16:24:48 3500 [Note] InnoDB: Setting log file .\ib_logfile101 size to 5 MB
2013-08-01 16:24:49 3500 [Note] InnoDB: Setting log file .\ib_logfile1 size to 5 MB
2013-08-01 16:24:49 3500 [Note] InnoDB: Renaming log file .\ib_logfile101 to .\ib_logfile0
2013-08-01 16:24:49 3500 [Warning] InnoDB: New log files created, LSN=45781
2013-08-01 16:24:49 3500 [Note] InnoDB: Doublewrite buffer not found: creating new
2013-08-01 16:24:49 3500 [Note] InnoDB: Doublewrite buffer created
2013-08-01 16:24:49 3500 [Note] InnoDB: 128 rollback segment(s) are active.
2013-08-01 16:24:49 3500 [Warning] InnoDB: Creating foreign key constraint system tables.
2013-08-01 16:24:49 3500 [Note] InnoDB: Foreign key constraint system tables created
2013-08-01 16:24:49 3500 [Note] InnoDB: Creating tablespace and datafile system tables.
2013-08-01 16:24:49 3500 [Note] InnoDB: Tablespace and datafile system tables created.
2013-08-01 16:24:49 3500 [Note] InnoDB: Waiting for purge to start
2013-08-01 16:24:49 3500 [Note] InnoDB: 5.6.12 started; log sequence number 0
2013-08-01 16:24:49 3500 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
2013-08-01 16:24:49 3500 [Note] - '127.0.0.1' resolves to '127.0.0.1';
2013-08-01 16:24:49 3500 [Note] Server socket created on IP: '127.0.0.1'.
2013-08-01 16:24:49 3500 [Warning] InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See [dev.mysql.com] for how you can resolve the problem.
2013-08-01 16:24:49 3500 [Warning] Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.
2013-08-01 16:24:49 3500 [Warning] InnoDB: Cannot open table mysql/slave_worker_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See [dev.mysql.com] for how you can resolve the problem.
2013-08-01 16:24:49 3500 [Warning] InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See [dev.mysql.com] for how you can resolve the problem.
2013-08-01 16:24:49 3500 [Warning] Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.
2013-08-01 16:24:49 3500 [Note] Event Scheduler: Loaded 0 events
2013-08-01 16:24:49 3500 [Note] C:\PROGRA~2\EASYPH~1.1VC\binaries\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.12-log' socket: '' port: 3306 MySQL Community Server (GPL)
2013-08-01 16:34:07 3408 [Note] Plugin 'FEDERATED' is disabled.
2013-08-01 16:34:07 d54 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-08-01 16:34:07 3408 [Note] InnoDB: The InnoDB memory heap is disabled
2013-08-01 16:34:07 3408 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-08-01 16:34:07 3408 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-08-01 16:34:07 3408 [Note] InnoDB: Not using CPU crc32 instructions
2013-08-01 16:34:07 3408 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-08-01 16:34:07 3408 [Note] InnoDB: Completed initialization of buffer pool
2013-08-01 16:34:07 3408 [Note] InnoDB: Highest supported file format is Barracuda.
2013-08-01 16:34:08 3408 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1600607 in the ib_logfiles!
2013-08-01 16:34:08 3408 [Note] InnoDB: Database was not shutdown normally!
2013-08-01 16:34:08 3408 [Note] InnoDB: Starting crash recovery.
2013-08-01 16:34:08 3408 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-08-01 16:34:08 3408 [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 teste/categories which uses space ID: 1 at filepath: .\teste\categories.ibd
InnoDB: Error: could not open single-table tablespace file .\teste\categories.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.
2013-08-01 16:34:16 3860 [Note] Plugin 'FEDERATED' is disabled.
2013-08-01 16:34:16 f18 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-08-01 16:34:16 3860 [Note] InnoDB: The InnoDB memory heap is disabled
2013-08-01 16:34:16 3860 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-08-01 16:34:16 3860 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-08-01 16:34:16 3860 [Note] InnoDB: Not using CPU crc32 instructions
2013-08-01 16:34:16 3860 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-08-01 16:34:16 3860 [Note] InnoDB: Completed initialization of buffer pool
2013-08-01 16:34:16 3860 [Note] InnoDB: Highest supported file format is Barracuda.
2013-08-01 16:34:16 3860 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1600607 in the ib_logfiles!
2013-08-01 16:34:16 3860 [Note] InnoDB: Database was not shutdown normally!
2013-08-01 16:34:16 3860 [Note] InnoDB: Starting crash recovery.
2013-08-01 16:34:16 3860 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-08-01 16:34:16 3860 [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 teste/categories which uses space ID: 1 at filepath: .\teste\categories.ibd
InnoDB: Error: could not open single-table tablespace file .\teste\categories.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.
2013-08-01 16:34:33 4064 [Note] Plugin 'FEDERATED' is disabled.
2013-08-01 16:34:33 fe4 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-08-01 16:34:33 4064 [Note] InnoDB: The InnoDB memory heap is disabled
2013-08-01 16:34:33 4064 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-08-01 16:34:33 4064 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-08-01 16:34:33 4064 [Note] InnoDB: Not using CPU crc32 instructions
2013-08-01 16:34:33 4064 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-08-01 16:34:33 4064 [Note] InnoDB: Completed initialization of buffer pool
2013-08-01 16:34:33 4064 [Note] InnoDB: Highest supported file format is Barracuda.
2013-08-01 16:34:33 4064 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1600607 in the ib_logfiles!
2013-08-01 16:34:33 4064 [Note] InnoDB: Database was not shutdown normally!
2013-08-01 16:34:33 4064 [Note] InnoDB: Starting crash recovery.
2013-08-01 16:34:33 4064 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-08-01 16:34:33 4064 [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 teste/categories which uses space ID: 1 at filepath: .\teste\categories.ibd
InnoDB: Error: could not open single-table tablespace file .\teste\categories.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.
2013-08-01 16:35:43 380 [Note] Plugin 'FEDERATED' is disabled.
2013-08-01 16:35:43 3d8 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-08-01 16:35:43 380 [Note] InnoDB: The InnoDB memory heap is disabled
2013-08-01 16:35:43 380 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-08-01 16:35:43 380 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-08-01 16:35:43 380 [Note] InnoDB: Not using CPU crc32 instructions
2013-08-01 16:35:43 380 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-08-01 16:35:43 380 [Note] InnoDB: Completed initialization of buffer pool
2013-08-01 16:35:43 380 [Note] InnoDB: Highest supported file format is Barracuda.
2013-08-01 16:35:43 380 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1600607 in the ib_logfiles!
2013-08-01 16:35:43 380 [Note] InnoDB: Database was not shutdown normally!
2013-08-01 16:35:43 380 [Note] InnoDB: Starting crash recovery.
2013-08-01 16:35:43 380 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-08-01 16:35:43 380 [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 teste/categories which uses space ID: 1 at filepath: .\teste\categories.ibd
InnoDB: Error: could not open single-table tablespace file .\teste\categories.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.
2013-08-01 16:35:48 2812 [Note] Plugin 'FEDERATED' is disabled.
2013-08-01 16:35:48 af8 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-08-01 16:35:48 2812 [Note] InnoDB: The InnoDB memory heap is disabled
2013-08-01 16:35:48 2812 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-08-01 16:35:48 2812 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-08-01 16:35:48 2812 [Note] InnoDB: Not using CPU crc32 instructions
2013-08-01 16:35:48 2812 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-08-01 16:35:48 2812 [Note] InnoDB: Completed initialization of buffer pool
2013-08-01 16:35:48 2812 [Note] InnoDB: Highest supported file format is Barracuda.
2013-08-01 16:35:48 2812 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1600607 in the ib_logfiles!
2013-08-01 16:35:48 2812 [Note] InnoDB: Database was not shutdown normally!
2013-08-01 16:35:48 2812 [Note] InnoDB: Starting crash recovery.
2013-08-01 16:35:48 2812 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-08-01 16:35:48 2812 [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 teste/categories which uses space ID: 1 at filepath: .\teste\categories.ibd
InnoDB: Error: could not open single-table tablespace file .\teste\categories.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.
2013-08-01 16:35:55 820 [Note] Plugin 'FEDERATED' is disabled.
2013-08-01 16:35:55 444 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-08-01 16:35:55 820 [Note] InnoDB: The InnoDB memory heap is disabled
2013-08-01 16:35:55 820 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-08-01 16:35:55 820 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-08-01 16:35:55 820 [Note] InnoDB: Not using CPU crc32 instructions
2013-08-01 16:35:55 820 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-08-01 16:35:55 820 [Note] InnoDB: Completed initialization of buffer pool
2013-08-01 16:35:55 820 [Note] InnoDB: Highest supported file format is Barracuda.
2013-08-01 16:35:55 820 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1600607 in the ib_logfiles!
2013-08-01 16:35:55 820 [Note] InnoDB: Database was not shutdown normally!
2013-08-01 16:35:55 820 [Note] InnoDB: Starting crash recovery.
2013-08-01 16:35:55 820 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-08-01 16:35:55 820 [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 teste/categories which uses space ID: 1 at filepath: .\teste\categories.ibd
InnoDB: Error: could not open single-table tablespace file .\teste\categories.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.
2013-08-01 16:36:03 3520 [Note] Plugin 'FEDERATED' is disabled.
2013-08-01 16:36:03 dc4 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-08-01 16:36:03 3520 [Note] InnoDB: The InnoDB memory heap is disabled
2013-08-01 16:36:03 3520 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-08-01 16:36:03 3520 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-08-01 16:36:03 3520 [Note] InnoDB: Not using CPU crc32 instructions
2013-08-01 16:36:03 3520 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-08-01 16:36:03 3520 [Note] InnoDB: Completed initialization of buffer pool
2013-08-01 16:36:03 3520 [Note] InnoDB: Highest supported file format is Barracuda.
2013-08-01 16:36:03 3520 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1600607 in the ib_logfiles!
2013-08-01 16:36:03 3520 [Note] InnoDB: Database was not shutdown normally!
2013-08-01 16:36:04 3520 [Note] InnoDB: Starting crash recovery.
2013-08-01 16:36:04 3520 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-08-01 16:36:04 3520 [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 teste/categories which uses space ID: 1 at filepath: .\teste\categories.ibd
InnoDB: Error: could not open single-table tablespace file .\teste\categories.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.
2013-08-01 16:36:20 3440 [Note] Plugin 'FEDERATED' is disabled.
2013-08-01 16:36:20 d64 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-08-01 16:36:20 3440 [Note] InnoDB: The InnoDB memory heap is disabled
2013-08-01 16:36:20 3440 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-08-01 16:36:20 3440 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-08-01 16:36:20 3440 [Note] InnoDB: Not using CPU crc32 instructions
2013-08-01 16:36:20 3440 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-08-01 16:36:20 3440 [Note] InnoDB: Completed initialization of buffer pool
2013-08-01 16:36:20 3440 [Note] InnoDB: Highest supported file format is Barracuda.
2013-08-01 16:36:20 3440 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1600607 in the ib_logfiles!
2013-08-01 16:36:20 3440 [Note] InnoDB: Database was not shutdown normally!
2013-08-01 16:36:20 3440 [Note] InnoDB: Starting crash recovery.
2013-08-01 16:36:20 3440 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-08-01 16:36:20 3440 [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 teste/categories which uses space ID: 1 at filepath: .\teste\categories.ibd
InnoDB: Error: could not open single-table tablespace file .\teste\categories.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.
Options: ReplyQuote


Your Name: 
Your Email: 
Subject: 
Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.