FYI, New MAMP 3.1 gets db error, here is solution
Permalink
I just upgraded my MAMP from 3.0.6 to 3.1.
All of sudden, my concrete5.7 went dead.
But here is simple solution from:
http://forumsarchive.laravel.io/viewtopic.php?id=1008...
You need to change the MySQL's db server address from "localhost" to "127.0.0.1" at
/application/config/database.php
It should solve the error.
New MAMP 3.1 somehow doesn't see MySQL server by hitting "localhost"
I just wasted my last 1 hr for this.. so don't waste time like me.
Good luck
All of sudden, my concrete5.7 went dead.
SQLSTATE[HY000] [2002] No such file or directory
But here is simple solution from:
http://forumsarchive.laravel.io/viewtopic.php?id=1008...
You need to change the MySQL's db server address from "localhost" to "127.0.0.1" at
/application/config/database.php
It should solve the error.
New MAMP 3.1 somehow doesn't see MySQL server by hitting "localhost"
I just wasted my last 1 hr for this.. so don't waste time like me.
Good luck
Thanks for that. I have been wondering what happened.
@tallacman,
Thanks!
Japanese users doesn't seem to have the same problem as I do.
HissyNC has MAMP PRO 3.1 installed.
And he has no problem with it.
I use my MAMP on my old Mac OS X that I kept migrating since Mac OS X Tiger back in 2007. So my Mac could be messed up.
But here is how I upgraded my MAMP...
It was, in fact, clean install.
I wiped MAMP 3.0.6 using AppCleaner, and installed MAMP 3.1 as a fresh copy.
So I assume that could have done something for it??
Thanks!
Japanese users doesn't seem to have the same problem as I do.
HissyNC has MAMP PRO 3.1 installed.
And he has no problem with it.
I use my MAMP on my old Mac OS X that I kept migrating since Mac OS X Tiger back in 2007. So my Mac could be messed up.
But here is how I upgraded my MAMP...
It was, in fact, clean install.
I wiped MAMP 3.0.6 using AppCleaner, and installed MAMP 3.1 as a fresh copy.
So I assume that could have done something for it??
OK.
I've contacted the MAMP Support.
They are aware of the bug at 3.1., and they are fixing the bug .
Here is the message from MAMP support.
> Hi,
>
> We currently have a bug that willl be fixed this week. In the meantime you
> need to add this line to your php.ini file
>
> pdo_mysql.default_socket = /Applications/MAMP/tmp/mysql/mysql.sock
>
> Your php.ini file for MAMP is located in
> /Applications/MAMP/bin/php/phpX.XX/conf
There you go.
I've contacted the MAMP Support.
They are aware of the bug at 3.1., and they are fixing the bug .
Here is the message from MAMP support.
> Hi,
>
> We currently have a bug that willl be fixed this week. In the meantime you
> need to add this line to your php.ini file
>
> pdo_mysql.default_socket = /Applications/MAMP/tmp/mysql/mysql.sock
>
> Your php.ini file for MAMP is located in
> /Applications/MAMP/bin/php/phpX.XX/conf
There you go.
