Proxysql: Detected a broken connection during SET NAMES, Can't initialize character set (null) (path: compiled_in)

Created on 24 Sep 2019  路  4Comments  路  Source: sysown/proxysql

Hi,

We keep getting this error message... Please anyone help...

2019-09-24 10:24:56 MySQL_Session.cpp:2543:handler_again___status_CHANGING_CHARSET(): [ERROR] Detected a broken connection during SET NAMES on 172.16.0.51 , 3306 : 2019, Can't initialize character set (null) (path: compiled_in)
Can't initialize character set (null) (path: compiled_in)
2019-09-24 10:24:56 MySQL_Session.cpp:2543:handler_again___status_CHANGING_CHARSET(): [ERROR] Detected a broken connection during SET NAMES on 172.16.0.51 , 3306 : 2019, Can't initialize character set (null) (path: compiled_in)
Can't initialize character set (null) (path: compiled_in)
2019-09-24 14:40:42 MySQL_Session.cpp:2543:handler_again___status_CHANGING_CHARSET(): [ERROR] Detected a broken connection during SET NAMES on 172.16.0.51 , 3306 : 2019, Can't initialize character set (null) (path: compiled_in)
Can't initialize character set (null) (path: compiled_in)
2019-09-24 14:40:42 MySQL_Session.cpp:2543:handler_again___status_CHANGING_CHARSET(): [ERROR] Detected a broken connection during SET NAMES on 172.16.0.51 , 3306 : 2019, Can't initialize character set (null) (path: compiled_in)
Can't initialize character set (null) (path: compiled_in)
2019-09-24 14:50:44 MySQL_Session.cpp:2543:handler_again___status_CHANGING_CHARSET(): [ERROR] Detected a broken connection during SET NAMES on 172.16.0.51 , 3306 : 2019, Can't initialize character set (null) (path: compiled_in)
Can't initialize character set (null) (path: compiled_in)
2019-09-24 14:50:45 MySQL_Session.cpp:2543:handler_again___status_CHANGING_CHARSET(): [ERROR] Detected a broken connection during SET NAMES on 172.16.0.51 , 3306 : 2019, Can't initialize character set (null) (path: compiled_in)
Can't initialize character set (null) (path: compiled_in)
2019-09-24 15:00:41 MySQL_Session.cpp:2543:handler_again___status_CHANGING_CHARSET(): [ERROR] Detected a broken connection during SET NAMES on 172.16.0.51 , 3306 : 2019, Can't initialize character set (null) (path: compiled_in)
Can't initialize character set (null) (path: compiled_in)
2019-09-24 15:08:13 MySQL_Session.cpp:2543:handler_again___status_CHANGING_CHARSET(): [ERROR] Detected a broken connection during SET NAMES on 172.16.0.51 , 3306 : 2019, Can't initialize character set (null) (path: compiled_in)
Can't initialize character set (null) (path: compiled_in)
2019-09-24 15:08:13 MySQL_Session.cpp:2543:handler_again___status_CHANGING_CHARSET(): [ERROR] Detected a broken connection during SET NAMES on 172.16.0.51 , 3306 : 2019, Can't initialize character set (null) (path: compiled_in)
Can't initialize character set (null) (path: compiled_in)
2019-09-24 15:20:41 MySQL_Session.cpp:2543:handler_again___status_CHANGING_CHARSET(): [ERROR] Detected a broken connection during SET NAMES on 172.16.0.51 , 3306 : 2019, Can't initialize character set (null) (path: compiled_in)
Can't initialize character set (null) (path: compiled_in)
2019-09-24 15:20:42 MySQL_Session.cpp:2543:handler_again___status_CHANGING_CHARSET(): [ERROR] Detected a broken connection during SET NAMES on 172.16.0.51 , 3306 : 2019, Can't initialize character set (null) (path: compiled_in)
Can't initialize character set (null) (path: compiled_in)
2019-09-24 15:30:42 MySQL_Session.cpp:2543:handler_again___status_CHANGING_CHARSET(): [ERROR] Detected a broken connection during SET NAMES on 172.16.0.51 , 3306 : 2019, Can't initialize character set (null) (path: compiled_in)
Can't initialize character set (null) (path: compiled_in)
2019-09-24 15:30:42 MySQL_Session.cpp:2543:handler_again___status_CHANGING_CHARSET(): [ERROR] Detected a broken connection during SET NAMES on 172.16.0.51 , 3306 : 2019, Can't initialize character set (null) (path: compiled_in)
Can't initialize character set (null) (path: compiled_in)
2019-09-24 15:46:01 MySQL_Session.cpp:2543:handler_again___status_CHANGING_CHARSET(): [ERROR] Detected a broken connection during SET NAMES on 172.16.0.51 , 3306 : 2019, Can't initialize character set (null) (path: compiled_in)
Can't initialize character set (null) (path: compiled_in)
2019-09-24 15:46:09 MySQL_Session.cpp:2543:handler_again___status_CHANGING_CHARSET(): [ERROR] Detected a broken connection during SET NAMES on 172.16.0.51 , 3306 : 2019, Can't initialize character set (null) (path: compiled_in)
Can't initialize character set (null) (path: compiled_in)
2019-09-24 15:46:09 MySQL_Session.cpp:2543:handler_again___status_CHANGING_CHARSET(): [ERROR] Detected a broken connection during SET NAMES on 172.16.0.51 , 3306 : 2019, Can't initialize character set (null) (path: compiled_in)
Can't initialize character set (null) (path: compiled_in)
2019-09-24 15:56:09 MySQL_Session.cpp:2543:handler_again___status_CHANGING_CHARSET(): [ERROR] Detected a broken connection during SET NAMES on 172.16.0.51 , 3306 : 2019, Can't initialize character set (null) (path: compiled_in)
Can't initialize character set (null) (path: compiled_in)
2019-09-24 16:23:20 MySQL_Session.cpp:2543:handler_again___status_CHANGING_CHARSET(): [ERROR] Detected a broken connection during SET NAMES on 172.16.0.51 , 3306 : 2019, Can't initialize character set (null) (path: compiled_in)
Can't initialize character set (null) (path: compiled_in)
2019-09-24 16:23:20 MySQL_Session.cpp:2543:handler_again___status_CHANGING_CHARSET(): [ERROR] Detected a broken connection during SET NAMES on 172.16.0.51 , 3306 : 2019, Can't initialize character set (null) (path: compiled_in)
Can't initialize character set (null) (path: compiled_in)
2019-09-24 16:33:57 MySQL_Session.cpp:2543:handler_again___status_CHANGING_CHARSET(): [ERROR] Detected a broken connection during SET NAMES on 172.16.0.51 , 3306 : 2019, Can't initialize character set (null) (path: compiled_in)
Can't initialize character set (null) (path: compiled_in)
2019-09-24 16:34:21 MySQL_Session.cpp:2543:handler_again___status_CHANGING_CHARSET(): [ERROR] Detected a broken connection during SET NAMES on 172.16.0.51 , 3306 : 2019, Can't initialize character set (null) (path: compiled_in)
Can't initialize character set (null) (path: compiled_in)
2019-09-24 16:34:21 MySQL_Session.cpp:2543:handler_again___status_CHANGING_CHARSET(): [ERROR] Detected a broken connection during SET NAMES on 172.16.0.51 , 3306 : 2019, Can't initialize character set (null) (path: compiled_in)
Can't initialize character set (null) (path: compiled_in)
2019-09-24 16:44:21 MySQL_Session.cpp:2543:handler_again___status_CHANGING_CHARSET(): [ERROR] Detected a broken connection during SET NAMES on 172.16.0.51 , 3306 : 2019, Can't initialize character set (null) (path: compiled_in)
Can't initialize character set (null) (path: compiled_in)
2019-09-24 16:44:21 MySQL_Session.cpp:2543:handler_again___status_CHANGING_CHARSET(): [ERROR] Detected a broken connection during SET NAMES on 172.16.0.51 , 3306 : 2019, Can't initialize character set (null) (path: compiled_in)
Can't initialize character set (null) (path: compiled_in)
2019-09-24 16:54:21 MySQL_Session.cpp:2543:handler_again___status_CHANGING_CHARSET(): [ERROR] Detected a broken connection during SET NAMES on 172.16.0.51 , 3306 : 2019, Can't initialize character set (null) (path: compiled_in)
Can't initialize character set (null) (path: compiled_in)
2019-09-24 16:54:21 MySQL_Session.cpp:2543:handler_again___status_CHANGING_CHARSET(): [ERROR] Detected a broken connection during SET NAMES on 172.16.0.51 , 3306 : 2019, Can't initialize character set (null) (path: compiled_in)

Most helpful comment

@cehau37 in cases mysql-handle_unknown_charset=1 did not help you (like it did not help me), you can circumvent this by using MySQL connector options (https://dev.mysql.com/doc/connector-cpp/1.1/en/connector-cpp-connect-options.html) by adding a preInit which will do it before driver initialization, e.g. doing "SET NAMES UTF8" in preInit (or other charset you may need).

To help somebody who got here Googling, I've encountered this exact error in MySQL Workbench 8 <> ProxySQL 2.0.8 <> MySQL 5.7 combination and this was the solution: In MySQL Connection / Server / Connection / Advanced / Others / preInit=set names utf8

All 4 comments

Error 2019 is a special error: the backend doesn't support the charset required by the client.
We just added a commit to adds more verbosity.

Dear @renecannao ,

thank you for this. it is now showing as below.

2019-11-12 13:48:34 MySQL_Session.cpp:2916:handler_again___status_CHANGING_CHARSET(): [ERROR] Can't initialize character set on 172.16.0.51, 3306: Error 2019 (Can't initialize character set 255). Closing connection.

Still not sure what it means by "Can't initialize character set 255"...

Please help...

Hi @cehau37 , I believe this comment is relevant to you:
https://github.com/sysown/proxysql/issues/1903#issuecomment-552673690 .
Specifically, you may need to turn mysql-handle_unknown_charset=1

@cehau37 in cases mysql-handle_unknown_charset=1 did not help you (like it did not help me), you can circumvent this by using MySQL connector options (https://dev.mysql.com/doc/connector-cpp/1.1/en/connector-cpp-connect-options.html) by adding a preInit which will do it before driver initialization, e.g. doing "SET NAMES UTF8" in preInit (or other charset you may need).

To help somebody who got here Googling, I've encountered this exact error in MySQL Workbench 8 <> ProxySQL 2.0.8 <> MySQL 5.7 combination and this was the solution: In MySQL Connection / Server / Connection / Advanced / Others / preInit=set names utf8

Was this page helpful?
0 / 5 - 0 ratings

Related issues

eightnoteight picture eightnoteight  路  4Comments

beebol picture beebol  路  3Comments

calind picture calind  路  3Comments

ShahriyarR picture ShahriyarR  路  3Comments

AshwiniAhire picture AshwiniAhire  路  3Comments