Problème démarrage MySQL avec EasyPHP

**Skima** · 30/10/2013, 09h42

Salut à tous,

J'ai installé easyphp sur ma machine et tout marchait très bien. Je l'ai éteins pendant la nuit et quand j'essaye de le relancer, MySQL plante et j'ai l'erreur suivante :

Code :

Sélectionner tout - Visualiser dans une fenêtre à part

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
2013-10-30 09:25:30 13196 [Note] Plugin 'FEDERATED' is disabled.
2013-10-30 09:25:30 1e2c 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-10-30 09:25:30 13196 [Note] InnoDB: The InnoDB memory heap is disabled
2013-10-30 09:25:30 13196 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-10-30 09:25:30 13196 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-10-30 09:25:30 13196 [Note] InnoDB: Not using CPU crc32 instructions
2013-10-30 09:25:30 13196 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-10-30 09:25:30 13196 [Note] InnoDB: Completed initialization of buffer pool
2013-10-30 09:25:30 13196 [Note] InnoDB: Highest supported file format is Barracuda.
2013-10-30 09:25:30 13196 [Note] InnoDB: The log sequence numbers 26534332 and 26534332 in ibdata files do not match the log sequence number 26536572 in the ib_logfiles!
2013-10-30 09:25:30 13196 [Note] InnoDB: Database was not shutdown normally!
2013-10-30 09:25:30 13196 [Note] InnoDB: Starting crash recovery.
2013-10-30 09:25:30 13196 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-10-30 09:25:30 13196 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mapnotes/device uses space ID: 2 at filepath: .\mapnotes\device.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.