Proxysql Connect MYSQL Socket

[zGansalloz]

| hostgroup_id | hostname | port | gtid_port | weight | status | compression | max_connections | max_replication_lag | use_ssl | max_latency_ms | comment | mem_pointer | gtid_port | weight | status | compression | max_$
+--------------+----------------------------+------+-----------+--------+--------+-------------+-----------------+---------------------+---------+----------------+---------+-------------+-----------+--------+--------+-------------+-----$
| 1 | /var/run/mysqld/mysql.sock | 0 | 0 | 1 | 0 | 0 | 1000 | 0 | 0 | 0 | | 0 | 0 | 1 | 0 | 0 | 1000$

MySQL_Monitor.cpp:4344:monitor_dns_resolver_thread(): [ERROR] An error occurred while resolving hostname: /var/run/mysqld/mysql.sock [-2]

[zGansalloz]

MySQL_Session.cpp:1667:handler_again___status_PINGING_SERVER(): [ERROR] Detected a broken connection while during ping on (1,/var/run/mysqld/mysql.sock,0,23)

I do not quite understand why these actions take place on the socket.

[renecannao]

MySQL_Monitor.cpp:4344:monitor_dns_resolver_thread(): [ERROR] An error occurred while resolving hostname: /var/run/mysqld/mysql.sock [-2]

This is clearly a bug, and likely easy to fix. We will follow up.

... handler_again___status_PINGING_SERVER() ...
I do not quite understand why these actions take place on the socket.

To keep alive free connections.

[zGansalloz]

ProxySQL version 2.5.1-90-gbedaa6c, codename Truls

which stable version do you recommend?

[renecannao]

2.5.1 is the latest stable.
2.5.2 is expected to be released soon.

[renecannao]

Closing, fixed in PR #4213