échec du démarrage de mysql

Bonjour,

quand je démarre wamp, l'icône reste en orange et j'ai constaté que c'est mysql qui ne démarre pas ; on a quand même le PHP mais phpMyAdmin ne démarre pas et dans le log de mysql, j'ai

Citation:

---

5316 [ERROR] InnoDB: Attempted to open a previously opened tablespace.

---

Et cela, même si j'ai redémarré juste avant le PC. Que puis-je faire ?

Il n'y a que ça dans le log ?

Ca faisait 2 jours que j'avais pas réessayé et là, y en a toute une tartine :

Citation:

---

2014-12-27 10:31:56 2624 [Note] Plugin 'FEDERATED' is disabled.
2014-12-27 10:31:56 2624 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-12-27 10:31:56 2624 [Note] InnoDB: The InnoDB memory heap is disabled
2014-12-27 10:31:56 2624 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-12-27 10:31:56 2624 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-12-27 10:31:56 2624 [Note] InnoDB: Not using CPU crc32 instructions
2014-12-27 10:31:56 2624 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-12-27 10:31:56 2624 [Note] InnoDB: Completed initialization of buffer pool
2014-12-27 10:31:57 2624 [Note] InnoDB: Highest supported file format is Barracuda.
2014-12-27 10:31:57 2624 [Note] InnoDB: The log sequence numbers 1626027 and 1626027 in ibdata files do not match the log sequence number 1626037 in the ib_logfiles!
2014-12-27 10:31:57 2624 [Note] InnoDB: Database was not shutdown normally!
2014-12-27 10:31:57 2624 [Note] InnoDB: Starting crash recovery.
2014-12-27 10:31:57 2624 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-12-27 10:31:57 2624 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace medecinesport/table_user uses space ID: 6 at filepath: .\medecinesport\table_user.ibd. Cannot open tablespace su_dev_eis/oldmachines which uses space ID: 6 at filepath: .\su_dev_eis\oldmachines.ibd
InnoDB: Error: could not open single-table tablespace file .\su_dev_eis\oldmachines.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.

---

(en fait, l'autre jour, y en avait plus aussi, mais je n'avais copié que l'erreur)

Dans ce que tu nous montres il y est écrit le problème et la manière de la corriger.
En résumé le fichier \su_dev_eis\oldmachines.ibd n'est pas accessible, soit à cause d'un problème de droits, soit parce qu'il est corrompu.

OK, sauf que je ne trouve pas ce fichier ; il est marqué qu'au pire, on peut le supprimer mais si je fais une recherche windows sur oldmachines.ibd, rien n'est trouvé...

Tu es donc dans le cas 3

Il n'y a pas de my.cnf donc j'ai été dans my.ini et dedans, il propose de décommenter les lignes qui commencent par innodb ; je l'ai fait et ai du modifier un chemin (justement, celui qui mène au fichier "ibdata" (sans extension)), mais maintenant, dans le log, j'ai l'erreur suivante :

Citation:

---

2014-12-27 14:48:43 4752 [ERROR] InnoDB: File C:\wwwin\mysql\mysql5.6.17\data\ibdata1: 'create' returned OS error 223. Cannot continue operation

---

alors que dans my.ini, j'ai mis

Code:

---

innodb_data_home_dir = C:\www\bin\mysql\mysql5.6.17\data\

---

en réalité, ça ne se voit pas ici, mais à la place de wwwin, il y a www caractère cabalistique in...

Pourquoi tu n'as pas fait simplement ce qui était demandé dans le rapport d'erreur au lieu de toucher à plein de choses ?

Je l'avais fait ; sauf que comme la ligne citée n'existait pas, je l'ai créée

Code:

---

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

# Uncomment the following if you are using InnoDB tables #innodb_data_home_dir = C:\www\bin\mysql\mysql5.6.17\data\ #innodb_data_file_path = ibdata1:10M:autoextend #innodb_log_group_home_dir = C:\mysql\data/ #innodb_log_arch_dir = C:\mysql\data/ # You can set .._buffer_pool_size up to 50 - 80 % # of RAM but beware of setting memory usage too high #innodb_buffer_pool_size = 16M #innodb_additional_mem_pool_size = 2M # Set .._log_file_size to 25 % of buffer pool size #innodb_log_file_size = 5M #innodb_log_buffer_size = 8M #innodb_flush_log_at_trx_commit = 1 #innodb_lock_wait_timeout = 50 innodb_force_recovery>0

---

Je viens de le refaire...et

Citation:

---

2014-12-27 16:58:01 8036 [Note] Plugin 'FEDERATED' is disabled.
2014-12-27 16:58:01 8036 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-12-27 16:58:01 8036 [Note] InnoDB: The InnoDB memory heap is disabled
2014-12-27 16:58:01 8036 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-12-27 16:58:01 8036 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-12-27 16:58:01 8036 [Note] InnoDB: Not using CPU crc32 instructions
2014-12-27 16:58:01 8036 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-12-27 16:58:01 8036 [Note] InnoDB: Completed initialization of buffer pool
2014-12-27 16:58:01 8036 [Note] InnoDB: Highest supported file format is Barracuda.
2014-12-27 16:58:01 8036 [Note] InnoDB: The log sequence numbers 1626027 and 1626027 in ibdata files do not match the log sequence number 1626037 in the ib_logfiles!
2014-12-27 16:58:01 8036 [Note] InnoDB: Database was not shutdown normally!
2014-12-27 16:58:01 8036 [Note] InnoDB: Starting crash recovery.
2014-12-27 16:58:01 8036 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-12-27 16:58:01 8036 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace medecinesport/table_user uses space ID: 6 at filepath: .\medecinesport\table_user.ibd. Cannot open tablespace su_dev_eis/oldmachines which uses space ID: 6 at filepath: .\su_dev_eis\oldmachines.ibd
InnoDB: Error: could not open single-table tablespace file .\su_dev_eis\oldmachines.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.

---

"> 0" ça voulait dire avec une valeure supérieure à 0 :P
http://dev.mysql.com/doc/refman/5.0/...-recovery.html

OK :mouarf::mouarf:

:resolu: