Bug #7542 MySQL Query Browser (and Administrator) does not connect with default settings

• Submitted: 27 Dec 2004 10:36
• Modified: 14 Apr 2005 22:53
• Reporter: Martin Skold
• Status: Can't repeat
• Category: MySQL Query Browser
• Severity: S2 (Serious)
• Assigned to: Alfredo Kojima
• CPU Architecture: Any

[27 Dec 2004 10:36] Martin Skold

Description:
The default settings for the MySQL server is to accept connections on /tmp/mysql.sock.
The MySQL Query Browser (and MySQL Administrator) tries to connect on /tmp/mysq.sock
(missing 'l'). This annoying default setting has been there for at least 6 months (for Administrator) and causes first time users and evaluators always fail on first attempt. 
This is unecessary since it gives a bad first impression (of an otherwise great tool) and must be very easy to fix.

How to repeat:
Try to connect with default settings.

Suggested fix:
Change default setting to connect to /tmp/mysql.sock

[27 Dec 2004 16:30] MySQL Verification Team

I wasn't able to repeat the behavior reported. I am ablet to
connect to  /tmp/mysql.sock.

[27 Dec 2004 20:55] Martin Skold

The problem was NOT that one cannot connect to /tmp/mysql.sock,
the problem is that the default setting is /tmp/mysq.sock (missing 'l').
This setting will make the first attempt for a user trying to connect after
just downloading the tool to fail!!
Just change the default setting to /tmp/mysql.sock

[27 Dec 2004 21:22] MySQL Verification Team

Thank you for the clarification. However at my side the MA tried to
/var/lib directory and not /tmp directory.

[14 Feb 2005 22:28] Seth Meranda

I have come across this issue as well. How do I fix it? I am unable to connect to the mySQL server with either querry browser or administrator, but I can connect through the command prompt.

[1 Mar 2005 16:43] Alfredo Kojima

Martin:

There is no /tmp/mysq.sock hardcoded in the sources, so it must be some value left in /etc/my.cnf or put by accident in the connect dialog (click Details in the connect dialog).

Seth:

Click on the Details button in the connection dialog and make sure that it has the correct value 
of the mysql socket. Usually it is at /tmp/mysql.sock or /var/lib/mysql/mysql.sock

I will change the code so that it will attempt to use the output of mysql_config --socket if there are no values specified for the Socket Path argument.

[14 Apr 2005 22:53] Alfredo Kojima

I am closing this bug as I cannot reproduce it and there were no recent followups to queries. 
Please reopen with additional comments if you think the bug is valid.