follow us on google+ follow us feedburner

FORUM
Please use the search function and/or read the FAQ first.

MYSQL Crashes in EasyPHP 13.1 Dev server



Posted by: Osama
May 07, 2013 06:55AM
I am using EasyPHP for the last 3,4 years and its a great wamp server. in the latest version 13.1, i am facing a problem on windows 8 when i start easyphp the mysql server stops with an error "unexpected end of mysql see the log file". and I am unable to resolve it.
Options: ReplyQuote
Posted by: markos
May 10, 2013 03:25PM
You need to change the user s permission for the EasyPHP directory

1. Go to 'Computer', open/view Drive C, then double click 'Program Files (x86)'.
2. Right click on 'EasyPHP-DevServer-13.1' folder then click 'Properties'.
3. On 'Security' tab click 'Edit' button.
4. Select the user that you are currently using.
5. Under 'Permissions for Users' box, tick 'Full control' on 'Allow' column.
6. And then click 'OK' button to apply the changes.
Options: ReplyQuote
Posted by: Osama
May 11, 2013 04:13AM
I have tried this as well, but with the same result
Options: ReplyQuote
Posted by: Cernocky
May 12, 2013 07:48PM
I have same problem, but on win7 (64) and i tried that too.
Options: ReplyQuote
Posted by: Cernocky
May 13, 2013 08:26AM
I reinstalled Easyphp and everything is fine.
Options: ReplyQuote
Posted by: TR@SOE
May 15, 2013 02:11AM
I had encountered the same problem on and on. It seems most likely it will happen when you shut down your PC without closing EasyPHP/MySQL first. It may seem to me a MySQL problem.

Now I have copied all the database files and also the SQL dump to a separate place. This may save me some time when MySQL in EasyPHP crashes.
Options: ReplyQuote
Posted by: TR@SOE
May 16, 2013 01:28AM
Further to my comments yesterday, today I encountered another MySQL crash. And here is how I rectify it:

1. Exit EasyPHP Server
2. Delete all ibd files resides in your mysql/data directory.
3. Restart the server, make sure it starts (but your MySQL will not be functioning correctly and thus the sites won't display correctly in most cases as there is no database available).
4. Stop/Exit the EasyPHP Server
5. Copy all the backup ibd files to its respective locations.
6. Restart EasyPHP Server.

It should work by now and all the site are back to normal.

Hope that helps.
Options: ReplyQuote
Posted by: lukas.staron
June 22, 2013 02:08PM
TR@SOE thank you very much, i forgot backup one database file and i think everythink's gone :)

You save my monthly work
Options: ReplyQuote
Posted by: Exoskeletor
July 14, 2013 12:51AM
every version has a problem. i cant upderstand why the developers dont check them better first. i have waste so much time in 5 pcs
This solution doesnt work for me



Edited 1 time(s). Last edit at 07/14/2013 01:03AM by Exoskeletor.
Options: ReplyQuote
August 01, 2013 09:40PM
"You need to change the user s permission for the EasyPHP directory"
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: Belkasse
July 23, 2013 11:43AM
hello, when i install easyphp 5.2.10 on Windows 8, mysql is running for the first time, but when i restart it he's not. But if i delete all the ibd data files, mysql it works for the first time only, but after i receive always the message error : unexpected end of mysql... see log file. what is the solution ? thanks
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.