MySQL Compatibility with MacOS Sierra

Question

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 before and it doesn't seem to be working correctly. (Now maybe I just set it up wrong, but the since the installer offers no advanced options that doesn't seem to be the case.)

I can create schemas and tables, but when I go to actually query the table nothing happens. The activity indicator spins endlessly. I took a look at Activity Monitor and it doesn't show mysqld actually doing anything—the whole setup just appears to be deadlocked. Any ideas?

Here's what I'm trying to use:

• MySQL Community Server 5.7.15
• MySQL Workbench 6.3.7
• macOS Sierra 10.12 (16A323)

Answer 1

I had this same issue. I found out that the first instance you open just continues to spin when trying to run simple select statements with what seems to be no reason. You cannot even close the tab once it is open without closing all of MySQL Workbench. However, if you open up the same instance again it seems to work fine.

Answer 2

UPDATE!

macOS High Sierra needs MySQL Workbench 6.3.10

See changelog for 6.3.10 version

---

SOLVED in version 6.3.9

Tested on:

macOS Sierra
Version 10.12.3 (16D32)

MySQL

Workbench 6.3.9
Version 6.3.9 build 10690321 CE (64 bits) Community
----> OK

Download: MySQL Workbench 6.3.9
^{Packages for Sierra (10.12) are compatible with El Capitan (10.11) and are Yosemite (10.10)}

Changelog : ^{among others...}

• In some cases, executing a query caused MySQL Workbench to become unresponsive when the host was macOS Sierra. (Bug #25036263, Bug #83658)

---

Original answer in code snippet below:

 I ***temporary*** solved changed the ***group*** of the application. I tried everything, uninstalling, reinstall, change many settings... finally I thought that must be something with the security... was not normal, I check firewall rules, nothing... And just in case, I try with file permission and it was there. I was installed in the ***admin group***. Changed to ***staff*** solve the problem. $ sudo chown <USER>:staff /Applications/MySQLWorkbench.app > <sup>Where of course, `<USER>` is **your** username</sup> Ex. $ sudo chown gmo:staff /Applications/MySQLWorkbench.app Tested and working! - Go back to admin group... problem came back. - Changed to staff again... problem solved. I hope this is a global solution, please check yours. ###Edit: Solution not stable, problem came back after a few attempts. Try with `root:admin`, the same... --- ### UPDATE *`Workaround until new version is release`* Roll back to 6.2 version and working good. Tested on: > macOS Sierra > Version 10.12 (16A323) MySQL > Workbench 6.3 > Version 6.3.7 build 1199 CE (64 bits) Community > http://dev.mysql.com/downloads/workbench/6.3.html > `----> FAILS` > <sup>*Randomly, even changing group or creating new instances.*</sup> > Workbench 6.2 > Version 6.2.5.0 build 397 (32 bits) Community > http://dev.mysql.com/downloads/workbench/6.2.html > `----> OK` > <sup>*Work as expected.*</sup>

Answer 3

In my case MySQL Workbench Community (GPL) for Mac OS X version 6.3.8 CE build 1228 (64 bit) with

sudo chown -R <USER>:staff /Applications/MySQLWorkbench.app

applied, fixed the problem.

Answer 4

It worked for me when I downgraded the version to 6.1.7 :)

But missing the quick action icons functionality in the old version :(

Answer 5

MySQL Workbench 6.3.9 现已推出（2/14/17）并且似乎解决了这个问题。

Answer 6

I had the same problem, but it was fixed after a reboot. Maybe worth trying.

Answer 7

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!

Answer 8

I had same problem and I digged all internet but dont resolved problem and then I decided use another workbench. I found "DBeaver - Universal Database Manager" official site : http://dbeaver.jkiss.org/ and free and its tolerable.

Answer 9

I got same problem on "macOS 10.12.3" installed "MySQL Workbench Community (GPL) for Mac OS X version 6.3.8 CE build 1228 (64 bit)". It's always not responding after working around I found that problem comes from MSQL Workbench is set "Default Target MySQL Version" wrong version.

Step 1: open Terminal and check your MYSQL Server version

mysql --version

My machine:

mysql Ver 14.14 Distrib 5.7.9 , for osx10.9 (x86_64) using EditLine wrapper

Step 2: Open MySQL Workbench tool then go to "MYSQLWorkbench" near Apple icon on menu

Step 3: Workbench Preferences -> Modeling -> MySQL -> Default Target MySQL Version: 5.6

Step 4: Change current default from 5.6 into 5.7.9 then OK Step 5: MYSQLWorkbench -> Quit -> Open and check result.

Hope this help someone.

Answer 10

如果 Jonathan 的解决方案不能解决您的问题，请尝试重新打开同一个 mysql 实例，这对我有用。

Answer 11

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.

Answer 12

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.

Answer 13

尝试使用 127.0.0.1 作为主机名，而不是 localhost。

Answer 14

On my Mac, sometimes I get the infinite spinner when I try to run queries or close several tabs.

What worked for me was deleting the auto saved workspaces. Delete all entries in ~/Library/Application\\ Support/MySQL/Workbench/sql_workspaces
or the ones that you know are causing a problem. It works fine after deleting these.

Answer 15

Ver 8.0.23 seems to work ok for me on MacOS 10.12.6 without workbench. I like SequelPro.

Answer 16

mysql workbench version 6.3.10 worked for sierra 10.12.6. Generally, backward compatibility exists ie, newer hardware can operate reasonably older version of software