MySQL Bugs: #45294: Connection is lost with 'reading initial communication packet' error.

Bug #45294	Connection is lost with 'reading initial communication packet' error.
Submitted:	3 Jun 2009 10:44	Modified:	27 Jul 2009 14:20
Reporter:	Darren Cassar	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Proxy	Severity:	S1 (Critical)
Version:	0.7.1	OS:	Solaris
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
Hi, I'm using 0.6.1 which works fine on my solaris 10 64bit x86 machine, but 0.7.1 can't establish a connection to my mysql instance. I ran both versions one after the other to make sure that the problem was with proxy not something I was missing on the machine.

shell> mysql --user=user -p -h hostname -P 4040
Enter password:
ERROR 2013 (HY000): Lost connection to MySQL server at 'reading initial communication packet', system error: 0

Running the proxy in debug mode gave me:
2009-06-03 18:14:59: (message) mysql-proxy 0.7.1 started
2009-06-03 18:14:59: (debug) chassis.c:974: current RLIMIT_NOFILE = 281474976710912 (hard: 577936297042459468)
2009-06-03 18:14:59: (debug) chassis.c:978: trying to set new RLIMIT_NOFILE = 281474976718848 (hard: 577936297042459468)
2009-06-03 18:14:59: (debug) chassis.c:986: set new RLIMIT_NOFILE = 281474976718848 (hard: 577936297042459468)
2009-06-03 18:15:07: (debug) [network-mysqld.c:784]: error on a connection (fd: -1 event: 0). closing client connection.

no errors, only debug ... apart from the error on connection at the last line which is still a debug message.

Both proxy versions are 32bit:
mysql-proxy-0.6.1-solaris10-x86-32bit
mysql-proxy-0.7.1-solaris10-x86-32bit

How to repeat:
start mysql proxy on a simple localhost port 3306 ie ./mysql-proxy and try connecting to it from another server.

Thank you for your bug report.

Verified as described.

Can you please run dtruss/truss on the MySQL Proxy and attach the output to the bug-report ?

Truss log attached.

Cheers
Darren

As I see you run 5.1.14-.17 which are one of the MySQL Servers with a buggy protocol implementation. In 0.7.0-.2 we deny to connect to it, silently. 

Does it work if you use a later or earlier MySQL Server as backend ?

See Bug#25371

If yes (see privous comment), this is a duplicate of http://bugs.mysql.com/bug.php?id=45167

We are using MySQL 5.1.17 because that is the branch Infobright have taken to develop their product on.

I will talk to the infobirght guys to see if they will be applying patches to this.

Cheers,
Darren

Kay Roepke writes: 
duplicate of Bug#45167