[debian-mysql] Bug#528959: mysql-proxy 0.7.0-2 does not remove socket after clean shutdown

Raoul Bhatia [IPAX] r.bhatia at ipax.at
Sat May 16 17:53:01 UTC 2009


Package: mysql-proxy
Version: 0.7.0-2
Severity: important

hi,

i am using mysql-proxy 0.7.0-2 compiled from current debian sid sources.

i want to use it to supply a mysql socket to connect to an internal
mysql server.

the socket does not exist:
> root at c01n02 ~ # ls -al /var/run/mysqld/mysqld.sock
> ls: cannot access /var/run/mysqld/mysqld.sock: No such file or directory

starting mysql-proxy and then quitting it with ctrl+c
> root at c01n02 ~ # /usr/sbin/mysql-proxy --proxy-backend-addresses=192.168.100.200:42006 --proxy-address=/var/run/mysqld/mysqld.sock
> 2009-05-16 19:42:25: (critical) chassis.c:968: could not raise RLIMIT_NOFILE to 8192, Invalid argument (22). Current limit still 1024.
> ^Croot at c01n02 ~ # 

now, i am checking if the socket is still there:
> root at c01n02 ~ # ls -al /var/run/mysqld/mysqld.sock
> srwxr-xr-x 1 root root 0 2009-05-16 19:42 /var/run/mysqld/mysqld.sock

mysql-proxy is not running anymore:
> root at c01n02 ~ # ps aux|grep -i mysql-proxy
> root      8417  0.0  0.0   5888   828 pts/0    S+   19:50   0:00 grep -i mysql-proxy

i try to restart mysql proxy with the same command line and get an
error:
> root at c01n02 ~ # /usr/sbin/mysql-proxy --proxy-backend-addresses=192.168.100.200:42006 --proxy-address=/var/run/mysqld/mysqld.sock
> 2009-05-16 19:46:25: (critical) chassis.c:968: could not raise RLIMIT_NOFILE to 8192, Invalid argument (22). Current limit still 1024.
> 2009-05-16 19:46:25: (critical) network-socket.c:504: bind(/var/run/mysqld/mysqld.sock) failed: Address already in use (98)

cheers,
raoul





More information about the pkg-mysql-maint mailing list