I have no idea where they went! But I found a backup I made a few days prior that contained them all, so I pasted them back in and now everything (MYSQL, drush, MAMP and Drupal) are all working Ok again. If you are using a MySQL database you dont need to use custom type, just. It turns out that there were files and sub-directories missing from my MAMP/db/mysql57 folder. Maybe you MAMP server is not running :slightsmile: - didnt you got that. Theres a dropdown menu in the PHP section to change. When you click it youll find the options to change ports, php, web server etc. Try it out In the MAMP menu theres a link to preferences. I am prompted for my Mac user password, which I enter, but I am then given the error:Īny help here would be greatly appreciated. The only thing that is currently solving the issue for me is changing the php version in MAMP preferences. For instance, wp plugin install -activate (doc) lets you. I don't entirely understand that response, but it looks like there is nothing running that I can 'kill'. WP-CLI provides a command-line interface for many actions you might perform in the WordPress admin. To find out the exact cause of the problem, you need to look in the MySQL log file located in /Applications/MAMP/logs/ or /Library/Application Support/appsolute. Some forums relating to the same error suggest I check and stop any other running MYSQL instances, but I don't appear to have any.ĥ01 11212 10699 0 12:31pm ttys000 0:00.00 grep mysql In that directory there is just one file titled. For solve it: Go on phpMyAdmin and empty the DB, navigate to MAMP installation folder and create a custom configuration file my.cnf under /application/. force recovery mode was on innodbforcerecovery 1. While figuring out what was going wrong in the my.cnf following settings were applied: increased innodbbufferpoolsize value: innodbbufferpoolsize 1024M. I checked that path, and there is no mysql.sock file there. Delete the database folder and its contents in your case the database name is wordpress: rm -r /Library/Application Support/. So the issue was solved and MySQL runs locally via MAMP 5.1. '/Applications/MAMP/tmp/mysql/mysql.sock' (2) ![]() You can find the log files here: C:MAMPlogs. If no other Apache processes are running and you still have problems with Apache not starting, check your Apache log file. I am prompted for the password, but after entering correct password I receive:ĮRROR 2002 (HY000): Can't connect to local MySQL server through socket Open Windows Task Manager and check if Apache server processes are running. This means the "Open WebStart page" option is greyed over and the Drupal path that would normally load the site just displays an error.īut if I try to login into MYSQL via Terminal: When opening MAMP the Apache Server starts, whereas the MYSQL Server does not start. ![]() Up until today MYSQL was working OK for months with 2 MAMP Drupal localhost builds.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |