You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the docker-mysql-proxysql setup with its default settings and connecting with the mysql command line client:
mysql>select now(); set lc_messages='en_US'; select now();
+---------------------+
| now() |
+---------------------+
| 2020-07-0905:23:09 |
+---------------------+1 row inset (0.01 sec)
Query OK, 0 rows affected (0.02 sec)
ERROR 9006 (Y0000): ProxySQL Error: connection is locked to hostgroup 0 but trying to reach hostgroup 1
From the ProxySQL log:
2020-07-09 05:23:09 MySQL_Session.cpp:6483:unable_to_parse_set_statement(): [WARNING] Unable to parse unknown SET query from client 172.18.0.1:33870. Setting lock_hostgroup. Please report a bug for future enhancements:set lc_messages='en_US'
This was found when testing why phpMyAdmin was hitting errors connecting through ProxySQL. Likely other clients that set lc_messages may hit the same problem.
If you are submitting a reproducible bug report, please provide:
A clear description of the issue
ProxySQL version 2.0.12
OS version macos
The steps to reproduce the issue
The full ProxySQL error log (default location: /var/lib/proxysql/proxysql.log)
The text was updated successfully, but these errors were encountered:
In #2943 we're talking about adding documentation for workarounds to GUI clients running set profiling=1. If it's decided that set lc_messages isn't going to be supported (or delayed on the roadmap) then it should be included in that documentation as well.
Because lc_messages is an unknown server variable for ProxySQL, a client that attempts to set that value will end up locking to hostgroup.
(Discovered through testing the problem reported in https://groups.google.com/forum/#!topic/proxysql/ih05FKDFnNk)
Using the docker-mysql-proxysql setup with its default settings and connecting with the mysql command line client:
From the ProxySQL log:
This was found when testing why phpMyAdmin was hitting errors connecting through ProxySQL. Likely other clients that set
lc_messages
may hit the same problem.If you are submitting a reproducible bug report, please provide:
/var/lib/proxysql/proxysql.log
)The text was updated successfully, but these errors were encountered: