MAMP : Mysql ne démarre plus !!! (Créer un compte)

Bonjour,

Ma configuration WP actuelle

• Version de PHP/MySQL : 7.1.1
• Thème utilisé : Evolve
• Extensions en place : redux
• Nom de l’hébergeur : local
• Adresse du site : local

Problème(s) rencontré(s) : Bonjour,

Je galère ! J’ai développé mon site wordpress en local en utilisant MAMP et je souhaite maintenant le déplacer sur un serveur OVH.

Mais MAMP refuse de démarrer Mysql. J’y ai passé plusieurs heures et je m’arrache les cheveux.

Le log de MAMP me dit qu’il ne peut pas ouvrir : ./wordpress/wp_commentmeta.ibd

Or ce fichier n’existe pas sur ma machine (j’ai fait une recherche approfondie avec easyfind)

donc je ne peux pas le restaurer (j’ai une sauvegarde Time Machine).

Le log me conseille aussi de modifier le fichier : « you can set innodb_force_recovery > 0 in my.cnf »

je l’ai fait cela ne donne rien. J’ai aussi viré tous les fichiers .ibd, sans plus de succès.

Je ne sais donc vraiment plus quoi faire.

Je pensais que le problème était arrivé lors de l’upgrade de mon Mac (de Yosemite vers El Capitan) mais le clone que j’ai fait avant l’upgrade présente les mêmes symptômes)

En espérant un conseil !!!

D’avance merci

voici le log de MAMP :

170411 19:02:02 mysqld_safe Starting mysqld daemon with databases from /Library/Application Support/appsolute/MAMP PRO/db/mysql56
2017-04-11 19:02:03 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use –explicit_defaults_for_timestamp server option (see documentation for more details).
2017-04-11 19:02:03 0 [Note] –secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2017-04-11 19:02:03 0 [Note] /Applications/MAMP/Library/bin/mysqld (mysqld 5.6.35) starting as process 2649 …
2017-04-11 19:02:03 2649 [Warning] Setting lower_case_table_names=2 because file system for /Library/Application Support/appsolute/MAMP PRO/db/mysql56/ is case insensitive
2017-04-11 19:02:03 2649 [Note] Plugin ‘FEDERATED’ is disabled.
2017-04-11 19:02:03 2649 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-04-11 19:02:03 2649 [Note] InnoDB: The InnoDB memory heap is disabled
2017-04-11 19:02:03 2649 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-04-11 19:02:03 2649 [Note] InnoDB: Memory barrier is not used
2017-04-11 19:02:03 2649 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-04-11 19:02:03 2649 [Note] InnoDB: Not using CPU crc32 instructions
2017-04-11 19:02:03 2649 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-04-11 19:02:03 2649 [Note] InnoDB: Completed initialization of buffer pool
2017-04-11 19:02:03 2649 [Note] InnoDB: Highest supported file format is Barracuda.
2017-04-11 19:02:03 2649 [Note] InnoDB: The log sequence numbers 17161136 and 17161136 in ibdata files do not match the log sequence number 26000603 in the ib_logfiles!
2017-04-11 19:02:03 2649 [Note] InnoDB: Database was not shutdown normally!
2017-04-11 19:02:03 2649 [Note] InnoDB: Starting crash recovery.
2017-04-11 19:02:03 2649 [Note] InnoDB: Reading tablespace information from the .ibd files…
2017-04-11 19:02:03 2649 [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 wordpress/wp_commentmeta which uses space ID: 1 at filepath: ./wordpress/wp_commentmeta.ibd
2017-04-11 19:02:03 7fff7b985300 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
InnoDB: Error: could not open single-table tablespace file ./wordpress/wp_commentmeta.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.
170411 19:02:03 mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended