Your message dated Wed, 08 Jun 2016 12:24:16 +0000
with message-id <[email protected]>
and subject line Bug#820173: Removed package(s) from unstable
has caused the Debian Bug report #679659,
regarding mysql-proxy crashes when it isn't able to connect to
proxy-backend-addresses
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
679659: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679659
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mysql-proxy
Version: 0.8.1-1.1+b1
Severity: important
Dear Maintainer,
after stopping one of the backends, mysql-proxy crashes when trying to connect
to that backend
Here's what mysql-proxy logged:
Jun 30 16:33:20 mailaspin1 mysql-proxy: 2012-06-30 16:33:20: (message)
mysql-proxy 0.8.1 started
Jun 30 16:33:20 mailaspin1 mysql-proxy: 2012-06-30 16:33:20: (debug) max open
file-descriptors = 1024
Jun 30 16:33:20 mailaspin1 mysql-proxy: 2012-06-30 16:33:20: (message) proxy
listening on port 172.22.50.151:3307
Jun 30 16:33:20 mailaspin1 mysql-proxy: 2012-06-30 16:33:20: (message) added
read/write backend: 172.22.50.151:3306
Jun 30 16:33:20 mailaspin1 mysql-proxy: 2012-06-30 16:33:20: (message) added
read-only backend: 172.22.50.150:3306
Jun 30 16:38:02 mailaspin1 mysql-proxy: 2012-06-30 16:38:02: (debug)
[network-mysqld.c:937]: error on a connection (fd: -1 event: 0). closing client
connection.
Jun 30 16:38:02 mailaspin1 mysql-proxy: 2012-06-30 16:38:02: (message)
proxy-plugin.c.1503: connect(172.22.50.151:3306) failed: Connection refused.
Retrying with different backend.
Jun 30 16:38:02 mailaspin1 mysql-proxy: 2012-06-30 16:38:02: (debug)
[network-mysqld.c:937]: error on a connection (fd: -1 event: 0). closing client
connection.
Jun 30 16:38:02 mailaspin1 kernel: [3876078.257858] mysql-proxy[3784]: segfault
at c ip b7761b30 sp bf8ed0d0 error 4 in
libmysql-proxy.so.0.0.0.old[b774c000+23000]
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (1001, 'testing')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages mysql-proxy depends on:
ii libc6 2.13-33
ii libevent-2.0-5 2.0.19-stable-3
ii libglib2.0-0 2.32.3-1
ii liblua5.1-0 5.1.5-2
mysql-proxy recommends no packages.
mysql-proxy suggests no packages.
-- Configuration Files:
/etc/default/mysql-proxy changed:
ENABLED="true"
OPTIONS="--keepalive --proxy-lua-script=/usr/share/mysql-proxy/rw-splitting.lua
--proxy-address=172.22.50.151:3307 --proxy-backend-addresses=172.22.50.151:3306
--proxy-read-only-backend-addresses=172.22.50.150:3306 --log-level=debug
--log-use-syslog --admin-username=myadmin --admin-password=myadminpasswd
--admin-lua-script=/usr/share/mysql-proxy/admin.lua"
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.8.1-1.1+rm
Dear submitter,
as the package mysql-proxy has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/820173
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
