MySQL Bugs: #51419: Mac socket connection fails

Bug #51419	Mac socket connection fails
Submitted:	23 Feb 2010 13:48	Modified:	21 Apr 2010 10:40
Reporter:	Mike Frank	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S3 (Non-critical)
Version:	5.2.16	OS:	MacOS
Assigned to:	Mike Lischke	CPU Architecture:	Any

Description:
Can connect with socket using
mysql --protocol=SOCKET --socket=/tmp/my.sock -u root
can connect with tcp from workbench
can't connect with socket in workbench

same issue here
http://forums.mysql.com/read.php?152,355233,355233#msg-355233

How to repeat:
on mac os x 10.6 WB 5.2.16 beta setup connection for socket with
mysql --protocol=SOCKET --socket=/tmp/my.sock -u root

Suggested fix:
Either 
1) fix 
2) tell me why it doesn't work and we should enhance error message
3) add error checking it we need more info to provide proper message
4) combo of above.

Same problem here. Standard MacOSX Snow Leopard with MySQL Community Server 5.1.44.  I can connect fine using the mysql commandline client as root. Fails to connect using WorkBench 5.2.16-beta installed from the DMG package.

Please fix!

Bug #51460 was marked as a duplicate of this one.

Thank you for the bug report. Verified just as described. WB gives weird error message:

Unknown MySQL server host '.' (1)

when trying to connect via socket.

Same issue here, I just made a post on the announcement page, my bad...

Was utilizing 5.2.15 fine, first attempt to connect to local MySQL database after upgrading to 5.2.16 failed.  Ran test and received the following error message:

"Can't connect to MySQL server on '.' (4)"

Connecting via TCP/IP has never worked for me, so I am dead in the water right now...

I am running MAMP Pro 1.8.3  Local socket is located at:

/Applications/MAMP/tmp/mysql/mysql.sock

However, changing it to 

/tmp/mysql.sock

Did not help.

MySQL start-up configuration:

[client]
socket		= /Applications/MAMP/tmp/mysql/mysql.sock

[mysqld]
socket		= /Applications/MAMP/tmp/mysql/mysql.sock
skip-locking
key_buffer = 16M
max_allowed_packet = 1M
table_cache = 64
sort_buffer_size = 512K
net_buffer_length = 8K
read_buffer_size = 256K
read_rnd_buffer_size = 512K
myisam_sort_buffer_size = 8M
bind-address = 127.0.0.1

MAMP_skip-networking_MAMP

server-id	= 1

[mysqldump]
quick
max_allowed_packet = 16M

[mysql]
no-auto-rehash

[isamchk]
key_buffer = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M

[myisamchk]
key_buffer = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M

[mysqlhotcopy]
interactive-timeout

Verified also on Linux.

Complete error message:

Your connection attempt failed for user 'root' from your host to server at :NULL: Unknown MySQL server host '.' (1)

Mike Mulligan: Im having the same problems with MAMP, and was having trouble getting TCP/IP to work, until I unchecked the "allow local access only" checkbox on the MySQL config screen of MAMP PRO. now TCPIP works..

Fixed in 5.2

This issue has not been fixed in 5.2 I can confirm that the socket connection method still does not work

Jon, a patch for the issue has been pushed to our source repository to fix it. That means you won't see it before the next release. My comment is only part of the protocol to tell our QA I'm done with this report.

An entry has been added to the 5.2.17 changelog:

It was not possible to connect to the MySQL server with MySQL Workbench if using sockets.