Ads were blocked - no problem. But keep in mind that developing HeidiSQL, user support and hosting takes time and money. You may want to send a donation instead.

Support for ProxySQL admin interface

Miroticey1's profile image Miroticey1 posted 2 years ago in General Permalink

ProxySQL[0] acts as a proxy for MySQL. It features two connections:

  • Default port 6033: normal MySQL protocol for proxying
  • Default port 6032: admin interface utilising the MySQL protocol

On the admin interface you use a SQL like language. You can connect to it with the mysql command line tool. HeidiSQL however fails to connect to the admin interface, because it relies on certain MySQL features. I get the message "SQL error (1045): no such function: CONNECTION_ID" when trying to connect.

Would it be possible to support the ProxySQL admin interface?

[0] https://github.com/sysown/proxysql/

mjb's profile image mjb posted 4 weeks ago Permalink

Can I add a vote of support for this please... it would be nice to be able to administer ProxySQL from HeidiSQL.

ansgar's profile image ansgar posted 4 weeks ago Permalink

I understand what the first one does, but for what purpose is the admin interface meant to work?

And does HeidiSQL connect to the normal interface on port 6033?

Ads were blocked - no problem. But keep in mind that developing HeidiSQL, user support and hosting takes time and money. You may want to send a donation instead.
mjb's profile image mjb posted 4 weeks ago Permalink

ProxySQL presents a set of internal databases and tables for its configuration, which is accessible via a mysql compatible interface on 6032.

This is where you configure backend servers, users, etc.

6033 is literally just the mysql connection to the backend database(s), proxied by ProxySQL - it works fine.

The problem is that the admin interface has a limited set of supported SQL commands. But, it would be really nice to be able to edit the configuration in the HeidiSQL table data viewer.

ansgar's profile image ansgar posted 4 weeks ago Permalink

Ok, but then that service listening on port 6033 is not compatible to the MySQL TCP/IP protocol, or?

Or, in other words: would someone be able to run the C API function mysql_real_connect() against that service?

mjb's profile image mjb posted 4 weeks ago Permalink

No, 6033 is mysql compatible. it's the frontend port for proxying to the backend:

mysql client -> 6033 -> proxysql -> 3306 -> mysql/mariadb backend server(s)

mysql client -> 6032 -> proxysql-admin

ansgar's profile image ansgar posted 4 weeks ago Permalink

Hm ok, in that case I would like to give it a test with HeidiSQL, probably this is fixable. Is there some demonstration purpose service on the net to which I may connect, or is there a Windows binary which I can install here?

We should actually proceed in a ticket. I just found there is already one: issue #350 - please go through that and add comments there about the current issues.

mjb's profile image mjb posted 4 weeks ago Permalink

I don't believe so - and there's no windows binary release at https://github.com/sysown/proxysql/releases , so looks like you'd need to use a linux host. The free tier of AWS would probably give you a lightsail instance that would suffice for testing.

If you're really stuck, drop me an email using the address on my account here, and I can probably stand something up for you that you can access easily.

Will head on over to the github ticket for further.

Please login to leave a reply, or register at first.




Ads were blocked - no problem. But keep in mind that developing HeidiSQL, user support and hosting takes time and money. You may want to send a donation instead.