Seguí a la segunda, pero en mi directorio Applications/MAMP/db/mysql/ no había ningún archivo llamado ib_logfileN sino una carpeta denominada mysql56 como indica ElCid en cuyo interior estaba el fichero ibdata1 de 79,7 MB que borré tras haber hecho copia de seguridad. Mysqli_real_connect(): (HY000/2002): No such file or directoryīuscando soluciones llegué a tu web 🙂 Probé tu solución primera sin éxito. #2002 – No such file or directory - El servidor no está respondiendo (o el zócalo local al servidor MySQL no está configurado correctamente).

Cuando la volví a instalar observé que el archivo index.php del directorio htdocs indicaba su última línea ‘Something is wrong with your MAMP installation :-(‘ y al intentar conectar mediante phpMyAdmin con las bases de datos el navegador mostraba este mensaje: Para clonar una Moodle descargué Moodle4Mac-34.dmg que viene con la versión MAMP 4.1.1 pero como había cosas que no funcionaban tuve que quitarla. Hace tiempo estuve trabajando con una versión MAMP antigua, que desinstalé de mi MacOS. Muchas gracias, Juanfra Aldasoro y ElCid. Please back up these before you delete them 🙂 The reason that I am writing this post is so that I can reference it in the future. In the finder go to Applications/MAMP/db/mysql/ and delete the last log file (look for a file named ib_logfileN – being N the log number). MAMP is a great tool for running servers locally, however, when you must export that site you have been developing locally and your database is huge, then you could have some problems with PHPMyAdmin.The instructions he shared are the following: If you are having trouble fixing this issue with the instructions above, many readers are being able to solve this problem thanks to the amazing fix shared by one of the commenters, ElCid. You can also use Hyper, a terminal app built by the amazing team. You can check if there are any MySQL processes running the “top” command. You can find that app under Applications/Utilities. Note: Terminal is the terminal emulator included in Apple’s OS X operating system. Then you’ll be able to start again your servers by hitting “Start Servers” in the MAMP app. Assuming that not many people hosts websites on OSX, you won’t have any collateral damage.Īll you need to do, is run a simple command on the terminal or hyper. Simply killing all MySQL processes and then starting the servers again. There’s an easy solution for this, a quick and tiny fix you can run as many times you need. Sometimes, it also happens when restarting your computer. I hate when I resume my computer after sleeping a few hours, and I get that annoying red light just beside “MySQL server” indicator. The only problem I often get with this platform, is that MySQL won’t start. That way I can work with loads of different projects in an organized manner. Personally, I love setting up and using virtual hosts & WordPress multisite.

I like the fact that is the faster and easier way to setup a low-maintenance development environment for OSX.

Click on MAMP default or 80 & 3306 button to setup the server / MySQL ports accordingly. Go to Ports tab when you are in the Preferences section. The fact is that the URL depends on the ports you choose to use for your local server. As many others WordPress developers out there, I use MAMP for local development. Many users confuse with the URL of localhost setup in MAMP.

Mamp update sql