MySQL Bugs: #38415: Proxy should remove listen socket on shutdown

Bug #38415	Proxy should remove listen socket on shutdown
Submitted:	28 Jul 2008 18:52	Modified:	9 Sep 2010 13:56
Reporter:	Kay Roepke	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Proxy: Core	Severity:	S2 (Serious)
Version:	0.7.0	OS:	Any
Assigned to:	Michael Schuster	CPU Architecture:	Any
Tags:	proxy, shutdown, socket

Description:
When the proxy is started with a UNIX socket as proxy-address, we leave the socket around after shutdown. This prevents the proxy to start up the next time.

How to repeat:
Start proxy with --proxy-address=/tmp/proxy.sock.
Shutdown proxy.
Restart with the same arguments.

Suggested fix:
Remove the socket when doing clean shutdown.

I would like to ++ this one. Using 0.6.1 and experiencing the same issue.

Also of note, when the socket is created, it does not have +W permissions for group and everyone. I have to chmod a+w on the socket before clients can connect to it.

When mysqld starts however, this is not necessary. Why is mysqld able to correctly create the socket for all to use but mysql-proxy is not doing so?

This simply is a bug.
I've added https://blueprints.launchpad.net/mysql-proxy/+spec/remove-unix-socket just in case someone from the community would like to help out with this problem.

Thank you for your comment!

Heidi Bergh-Hoff writes: 
This bug should be fixed together with PR-43

Mark Leith writes: 
This should be tested in the 0.8.1 build, it was pushed some time ago:

https://code.launchpad.net/~schuster/mysql-proxy/remove_unix_socket/+merge/23652

Diego Medina writes: 
verified fixed on 0.8.1

A note has been added to the 0.8.1 changelog:

        When using <command>mysql-proxy</command> with a UNIX socket,                                                                    
        the socket would not be deleted                                                                                                  
        when <command>mysql-proxy</command> terminated.