J'ai un problème depuis ce matin avec mon serveur uWamp. Il parvient pas à ce mettre en ligne, mais j'ai trouvé un fichier log du mysql dont le voici :
<spoiler>
2013-07-19 10:03:55 2968 [Note] Plugin 'FEDERATED' is disabled.
2013-07-19 10:03:55 2968 [Note] InnoDB: The InnoDB memory heap is disabled
2013-07-19 10:03:55 2968 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-07-19 10:03:55 2968 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-07-19 10:03:55 2968 [Note] InnoDB: Not using CPU crc32 instructions
2013-07-19 10:03:55 2968 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2013-07-19 10:03:55 2968 [Note] InnoDB: Completed initialization of buffer pool
2013-07-19 10:03:56 2968 [Note] InnoDB: Highest supported file format is Barracuda.
2013-07-19 10:03:56 2968 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2961855 in the ib_logfiles!
2013-07-19 10:03:56 2968 [Note] InnoDB: Database was not shutdown normally!
2013-07-19 10:03:56 2968 [Note] InnoDB: Starting crash recovery.
2013-07-19 10:03:56 2968 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-07-19 10:04:01 2968 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace holo/bans uses space ID: 2 at filepath: .\holo\bans.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.
2013-07-19 10:06:45 4176 [Note] Plugin 'FEDERATED' is disabled.
2013-07-19 10:06:45 4176 [Note] InnoDB: The InnoDB memory heap is disabled
2013-07-19 10:06:45 4176 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-07-19 10:06:45 4176 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-07-19 10:06:45 4176 [Note] InnoDB: Not using CPU crc32 instructions
2013-07-19 10:06:45 4176 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2013-07-19 10:06:45 4176 [Note] InnoDB: Completed initialization of buffer pool
2013-07-19 10:06:45 4176 [Note] InnoDB: Highest supported file format is Barracuda.
2013-07-19 10:06:45 4176 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2961855 in the ib_logfiles!
2013-07-19 10:06:45 4176 [Note] InnoDB: Database was not shutdown normally!
2013-07-19 10:06:45 4176 [Note] InnoDB: Starting crash recovery.
2013-07-19 10:06:45 4176 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-07-19 10:06:45 4176 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace holo/bans uses space ID: 2 at filepath: .\holo\bans.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.
2013-07-19 10:07:52 5088 [Note] Plugin 'FEDERATED' is disabled.
2013-07-19 10:07:52 5088 [Note] InnoDB: The InnoDB memory heap is disabled
2013-07-19 10:07:52 5088 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-07-19 10:07:52 5088 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-07-19 10:07:52 5088 [Note] InnoDB: Not using CPU crc32 instructions
2013-07-19 10:07:52 5088 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2013-07-19 10:07:52 5088 [Note] InnoDB: Completed initialization of buffer pool
2013-07-19 10:07:52 5088 [Note] InnoDB: Highest supported file format is Barracuda.
2013-07-19 10:07:52 5088 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2961855 in the ib_logfiles!
2013-07-19 10:07:52 5088 [Note] InnoDB: Database was not shutdown normally!
2013-07-19 10:07:52 5088 [Note] InnoDB: Starting crash recovery.
2013-07-19 10:07:52 5088 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-07-19 10:07:52 5088 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace holo/bans uses space ID: 2 at filepath: .\holo\bans.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.
