Bug #39628 Debian Etch backports - failover does not work
Submitted: 24 Sep 2008 13:32 Modified: 24 Sep 2008 19:59
Reporter: Jean-Christophe Heger Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Proxy: Core Severity:S3 (Non-critical)
Version:0.6.1 OS:Linux
Assigned to: CPU Architecture:Any

[24 Sep 2008 13:32] Jean-Christophe Heger
Description:
Failover does not work with mysql-proxy 0.6.1 on Debian Etch (backports). When a server goes down, the proxy does not exclude it and return the error to the client. Regarding the documentation (http://dev.mysql.com/doc/refman/5.0/en/mysql-proxy-using.html), mysql-proxy does not work as expected.

Load balancing work correctly.

Message on the proxy:
network-mysqld-proxy.c.3709: connect(10.160.200.20:3306) failed: Connection refused

Message on the client:
ERROR 2013 (HY000): Lost connection to MySQL server at 'reading initial communication packet', system error: 0

Command line:
mysql-proxy \
  --proxy-backend-addresses=10.160.200.20:3306 \
  --proxy-backend-addresses=10.160.200.21:3306

Versions:
- mysql-proxy       0.6.1-1~bpo40+1
- mysql-server-5.0  5.0.51a-15~bpo40+1 

How to repeat:
mysql-proxy \
  --proxy-backend-addresses=10.160.200.20:3306 \
  --proxy-backend-addresses=10.160.200.21:3306
[24 Sep 2008 19:59] Sveta Smirnova
Please do not submit the same bug more than once. An existing bug report already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely
to be the same. Because of this, we hope you add your comments to the original bug instead.

Thank you for your interest in MySQL.

Duplicate of bug #34793