Note that there are some explanatory texts on larger screens.

plurals
  1. POMySQL OSX Lion - cannot connect after restart
    primarykey
    data
    text
    <p>Just upgraded a MBP 2009 from Snow Leopard to Lion. MySQL seems to be acting weird after the install. I've tried this on almost ALL possible ways to install MySQL (XAMPP, AMPPS, Homebrew and the official 64-bit DMG from Mysql.com) and they all exhibit the same behavior.</p> <p>The first start of MySQL (from all the packages above), everything is good. I use SequelPro to connect so the connection is fairly basic => Host: 127.0.0.1, User: root, Password: [blank] <em>... (AMPPs is "mysql")</em> I start/stop the MySQL server and everything seems to be ok.</p> <p>The next step is to import a new database. So create a database (UTF-8), click on the database and do IMPORT (using a .sql file). Everything still works. I stop the MySQL server and start it again. A .pid file gets generated, the .err file looks correct. I fire up SequelPro again and now it cannot connect to the MySQL server. Doing a ps -ef | grep mysql shows that everything is fine (running process matches the .pid file). I tried setting up the mysql.sock file to /tmp/mysql.sock (and other places) to no avail.</p> <p>The funny thing is that this just started happening on OSX Lion -- and I've tried ALL the packages above. The only way I have been able to work around it is to keep moving /Applications/XAMPP to the trash and re-installing and doing a new import and NOT shut down the MySQL server. The minute I have to shut it down or reboot, I have to re-install XAMPP all over again.</p> <p>Any ideas on why this could be happening?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload