Does anybody know of any compatibility issues or quirks with MySQL Community Server/Workbench on macOS Sierra? I recently did an installation on a Mac that had never held MySQL
try using 127.0.0.1 as the hostname, instead of localhost.
I had the same problem, but it was fixed after a reboot. Maybe worth trying.
MySQL Workbench 6.3.9 is available now (2/14/17) and appears to fix this problem.
I think I figured it out! It could have something to do with the length of the password. At first I had just set it up with a single-character password for my convenience, but I ran into some issues when trying to connect the Eclipse BIRT reporting software with MySQL. I changed the password to make it longer, and that solved the problem with BIRT, but even better, it seems to have solved the problem with Workbench as well!
I upgraded mine from 6.2.12 to 6.3.7 and that did the trick for me.
I will note that opening a 2nd tab for the same instance did work, but I found that I could never close the first and it always hung on any query. And... trying even quit out of the app would require me to force-kill it. Not an acceptable flow in my opinion, so the upgrade was important to me. My guess is that the install correctly set permissions or user groups.
This problem seems to be happening only when using MySQL Workbench. If you use the command line client (/usr/local/mysql/bin/mysql), it is possible to get an answer from mysql server.
Try to do it: 1. Execute /usr/local/mysql/bin/mysql --user=YOUR_USER --password=YOUR_PASSWORD 2. Type "use sys;" 3. Type "select * from sys_config;"
Now, we have to find out why the Workbench doesn't work.