Bug #53711 Saving /etc/my.cnf locks up mysql workbench and /usr/bin/login
Submitted: 17 May 2010 16:03 Modified: 31 Jul 2013 3:48
Reporter: Yuen Ho Wong Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: Administration Severity:S2 (Serious)
Version:5.2.25 GA OS:MacOS (10.6)
Assigned to: CPU Architecture:Any

[17 May 2010 16:03] Yuen Ho Wong
Description:
Everytime I press apply changes to the mysql file pane while adminstrating a server, mysql workbench fails to give me a ask for admin password pane and locks up the whole app. Force quitting it results in a zombie login process that stops me from applying credentials neither from Terminal.app nor Cocoa.

How to repeat:
1. Double click on a server instance under server administration
2. Click on confguration pane
3. Press apply
4. Press apply again
[28 May 2010 11:24] Geert Vanderkelen
What are the file permissions of the MySQL Configuration file? And the directory?

  shell> ls -ld /path/to/your/
  shell> ls -l /path/to/your/my.cnf

If the file can't be written, my WorkBench 5.2.21 on MacOS X 10.6 gives me a Permission Denied error, and just continues fine.
[29 May 2010 3:08] Yuen Ho Wong
The permissions is -rw-r--r-- root wheel.  There's no permission denied error or a dialog asking me for permission. It just hangs. I happen to find that anything that requires permission elevation fails to give me a dialog and then hangs.

I'm using 32bit MySQL WB with a 64bit MySQL BTW.
[23 Jun 2010 11:00] Susanne Ebrecht
Do you still have this problem by using Workbench 5.2.24?
[23 Jun 2010 16:18] Yuen Ho Wong
Yes this problem still persists on 5.2.24RC
[24 Jun 2010 6:41] Susanne Ebrecht
Please provide your instance configuration file:

server_instances.xml
[1 Jul 2010 4:27] Yuen Ho Wong
Where can I find this file? I don't see it in my home folder, /Application/MySQLWorkbench or /etc.
[1 Jul 2010 14:33] Maksym Yehorov
Can you try the following:

1. open Terminal window.
2. run there:
    > export DEBUG_ADMIN=5
3. Try to locate workbench and run it (<INSTALL PATH>/MySQLWorkbench.app/Contents/MacOS/MySQLWorkbench)
4. When it hangs copy the terminal output and attach to the bug report.

That will help us to track down the issue.

Thanks!
[8 Jul 2010 6:52] Yuen Ho Wong
debug log

Attachment: mysqlwb.log (application/octet-stream, text), 10.13 KiB.

[8 Jul 2010 7:00] Yuen Ho Wong
The above log message was produced by the following sequence:

1. Make sure "Automatically Start MySQL Server on Startup" is unchecked in System Preference > MySQL
2. reboot and login
3. Make sure MySQL is stopped
4. open terminal
5. export DEBUG_ADMIN=5
6. /Applications/MySQLWorkbench.app/Contents/MacOS/MySQLWorkbench
7. double click the server instance root@localhost under Server Administration
8. A popup box pops up that says:

Could not connect to MySQL Server at root@None

Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)
You can continue but some functionality may be unavailable.

9. Click Continue Anyway
10. Click start server
11. The above log message is produced, during the process, there was no pop up box asking me to input my sudo password.

Thanks!
[10 Aug 2010 8:53] Susanne Ebrecht
Please send output from
SHOW VARIABLES LIKE '%socket%';
SHOW VARIABLES LIKE '%port%';
[29 Aug 2010 14:21] Yuen Ho Wong
Please note that this bug can only be reproduced when the server is stopped. So there shouldn't be a socket or port active. When the server is running, here's the result from the queries:

mysql>show variables like '%socket%';
+---------------+-----------------+
| Variable_name | Value           |
+---------------+-----------------+
| socket        | /tmp/mysql.sock |
+---------------+-----------------+
1 row in set (0.00 sec)

[root@localhost] 5.1.48-log [(none)]
mysql>show variables like '%port%';
+---------------------+-------+
| Variable_name       | Value |
+---------------------+-------+
| innodb_support_xa   | ON    |
| large_files_support | ON    |
| port                | 3306  |
| report_host         |       |
| report_password     |       |
| report_port         | 3306  |
| report_user         |       |
+---------------------+-------+
7 rows in set (0.00 sec)

[root@localhost] 5.1.48-log [(none)]
mysql>
[13 Sep 2010 4:40] Alfredo Kojima
Can you check the KeyChain Access tool and look for any entry that looks like sudo@localhost or something similar and then delete it? Then retry. I am able to repeat something similar, but only when I enter an empty or wrong password in the password dialog. Maybe in your case there already is some wrong password stored/cached in the keychain, which is passed to sudo.

However, the lockup of everything in Terminal.app (which I also could repeat) is very odd and smells like a bug from MacOSX.
[20 Sep 2010 17:15] Yuen Ho Wong
I think this is exactly the problem. I was able to solve this problem by deleting all the passwords in keychain.
[31 Jul 2013 3:48] Philip Olson
Fixed as of MySQL Workbench 6.0.4, and here's the changelog entry:

MySQL Workbench could exhibit an extended timeout when suffering from
incorrect permissions. This extended timeout was fixed, and MySQL Workbench
will now ask for the sudo password when needed.

Thank you for the bug report.