Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unexpected packet from client, disconnecting the client #1689

Open
olafz opened this issue Sep 13, 2018 · 1 comment
Open

Unexpected packet from client, disconnecting the client #1689

olafz opened this issue Sep 13, 2018 · 1 comment

Comments

@olafz
Copy link

olafz commented Sep 13, 2018

We are experiencing a reproducible bug in ProxySQL with our setup and data. We have an application connecting to a ProxySQL instance and issuing lots of queries. This all works just fine, until a certain point where the ProxySQL logs

MySQL_Session.cpp:2427:handler(): [ERROR] Unexpected packet from client, disconnecting the client

At the same moment, the application logs an error because it's client connection is killed.

screen shot 2018-09-13 at 12 51 53

We are running ProxySQL version 1.4.9 on Debian linux.

We have a TCPDump of the specific TCP flow, but so far nothing seems wrong there and similar queries work on other places. That seems to suggest it's in some state of the proxy or maybe even in the data.

I can send the full TCPDump file.

@Reiner030
Copy link

Looks like same problem as #1600
which seems to be finally same problem as issue i answered there:

it could be that you also have multiplexing off and your backend is perhaps disconnected?
Then it could be a problem that the backend connection is "sticky" and therefore ProxySQL must hook off the connection to the client like here explained:
#1632 (comment) / #1632 (comment)

(I have this problem also in our environment from time to time if there is some network stuck in WAN connection...)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants