Je rencontre l'erreur #2002 en voulant lançant mon MySQL. L'icone de wamp est orange bien que ça démarré. Le serveur Apache quant à lui marche parfaitement. Prière m'aider. Voici une copie du fichier log de MySQL. 2015-04-18 09:24:53 11564 [Note] Plugin 'FEDERATED' is disabled. 2015-04-18 09:24:53 11564 [Note] InnoDB: Using atomics to ref count buffer pool pages 2015-04-18 09:24:53 11564 [Note] InnoDB: The InnoDB memory heap is disabled 2015-04-18 09:24:53 11564 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 2015-04-18 09:24:53 11564 [Note] InnoDB: Compressed tables use zlib 1.2.3 2015-04-18 09:24:53 11564 [Note] InnoDB: Not using CPU crc32 instructions 2015-04-18 09:24:53 11564 [Note] InnoDB: Initializing buffer pool, size = 128.0M 2015-04-18 09:24:53 11564 [Note] InnoDB: Completed initialization of buffer pool 2015-04-18 09:24:53 11564 [Note] InnoDB: Highest supported file format is Barracuda. 2015-04-18 09:24:53 11564 [Note] InnoDB: The log sequence numbers 21311601 and 21311601 in ibdata files do not match the log sequence number 30182635 in the ib_logfiles! 2015-04-18 09:24:53 11564 [Note] InnoDB: Database was not shutdown normally! 2015-04-18 09:24:53 11564 [Note] InnoDB: Starting crash recovery. 2015-04-18 09:24:53 11564 [Note] InnoDB: Reading tablespace information from the .ibd files... 2015-04-18 09:24:53 11564 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace esigila/main_associations uses space ID: 312 at filepath: .\esigila\main_associations.ibd. Cannot open tablespace moodle/mdl_assignfeedback_editpdf_annot which uses space ID: 312 at filepath: .\moodle\mdl_assignfeedback_editpdf_annot.ibd InnoDB: Error: could not open single-table tablespace file .\moodle\mdl_assignfeedback_editpdf_annot.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. 2015-04-18 09:25:39 9552 [Note] Plugin 'FEDERATED' is disabled. 2015-04-18 09:25:39 9552 [Note] InnoDB: Using atomics to ref count buffer pool pages 2015-04-18 09:25:39 9552 [Note] InnoDB: The InnoDB memory heap is disabled 2015-04-18 09:25:39 9552 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 2015-04-18 09:25:39 9552 [Note] InnoDB: Compressed tables use zlib 1.2.3 2015-04-18 09:25:39 9552 [Note] InnoDB: Not using CPU crc32 instructions 2015-04-18 09:25:39 9552 [Note] InnoDB: Initializing buffer pool, size = 128.0M 2015-04-18 09:25:39 9552 [Note] InnoDB: Completed initialization of buffer pool 2015-04-18 09:25:39 9552 [Note] InnoDB: Highest supported file format is Barracuda. 2015-04-18 09:25:39 9552 [Note] InnoDB: The log sequence numbers 21311601 and 21311601 in ibdata files do not match the log sequence number 30182635 in the ib_logfiles! 2015-04-18 09:25:39 9552 [Note] InnoDB: Database was not shutdown normally! 2015-04-18 09:25:39 9552 [Note] InnoDB: Starting crash recovery. 2015-04-18 09:25:39 9552 [Note] InnoDB: Reading tablespace information from the .ibd files... 2015-04-18 09:25:39 9552 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace esigila/main_associations uses space ID: 312 at filepath: .\esigila\main_associations.ibd. Cannot open tablespace moodle/mdl_assignfeedback_editpdf_annot which uses space ID: 312 at filepath: .\moodle\mdl_assignfeedback_editpdf_annot.ibd InnoDB: Error: could not open single-table tablespace file .\moodle\mdl_assignfeedback_editpdf_annot.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.
A priori, il semblerait qu'une de vos bases de données ou une table de type ENGINE = INNODB soit « vérolée ». Donc, comme indiqué dans les messages d'erreurs, dans le fichier wamp/bin/mysql/mysqlx.y.z/my.ini, mettre, juste avant [mysqldump] : innodb_force_recovery= valeur supérieure à 0 (Commencer avec 1) et bien lire [dev.mysql.com]
Néanmoins, la meilleure chose à faire serait d'importer une sauvegarde de vos tables, si vous en avez.
Je vous conseille de supprimer la table en question qui pose problème. Redémarrer wampserver et vérifiez que voys avez bien l'icône verte.
Ensuite, réinstallez là en passant par "import" de phpmyadmin.
Sinon, est-ce que InnoDB est bien configuré dans "my.ini" ?
@+
---------------------------------------------------------------------------------------------------------------------------------------------------------------- Mon site : [www.jcz.fr]
MERCI. En supprimant les bases de données en question. ça marche parfaitement. Mais maintenant j'ai un autre problème encore plus bisarre. je peux accéder au local host mais quand je veux ouvrir un de mes projets, cela ne s'affiche pas; la page d'erreur me dit : ERR_NAME_NOT_RESOLVED. Et en affichant les détails, j'ai :
impossible de trouver le serveur de NOM_DU_PROJET, car la résolution DNS a échoué. DNS est le service Web qui convertit les noms de sites Web en adresses Internet. Cette erreur est généralement due à l'absence de connexion Internet ou à une configuration incorrecte du réseau. Elle peut également être causée par un serveur DNS qui ne répond pas ou par un pare-feu qui interdit l'accès de Google Chrome au réseau.