ProxySQL DB Version Issues

[HANDL_Eric]

Hello,

we're in the process of attempting to migrate from an internally hosted MariaDB instance to an external database behind a ProxySQL instance. We noticed that Zabbix seems to be detecting an engine version from ProxySQL which is being returned and flagged as unsupported despite the backend database being on 10.11.8

As such to work around this, we added AllowUnsupportedDBVersions=1 to our server.config file and rebooted, but it doesn't seem to be doing anything as the service is still complaining about an unsupported DB version and won't start. Has anyone else run into this or know of a work around? We're running Zabbix v7.0.7 if that changes anything.

[HANDL_Eric]

Anybody? Id be happy to move this post if there is a better sub forum for this, was just looking to see if it was actually a problem or if we just missed a step.

[cyber]

Nothing wrong with subforum... Probably noone around, who has been using ProxySQL (I heard about it just now, reading this..:P)...
Does it return DB versions properly? Maybe its not the case of unsupported version (numbers), but unsupported DB engine (not mysql, mariadb or PG)? Maybe it just hides, whats behind it? Very random questions, I just don't know the system..

[HANDL_Eric]

Nothing wrong with subforum... Probably noone around, who has been using ProxySQL (I heard about it just now, reading this..:P)...
Does it return DB versions properly? Maybe its not the case of unsupported version (numbers), but unsupported DB engine (not mysql, mariadb or PG)? Maybe it just hides, whats behind it? Very random questions, I just don't know the system..

Thanks for the response sir! ProxySQL is exactly as the name sounds, a proxy for SQL connections. It's very much like a traditional load balancer but much more capable of making performance based routing decisions far beyond the up/down status of the database. In this case, there are 3 nodes of MariaDB v10.11.8 running in a multi-writer cluster. ProxySQL is the thing that sits in front of it to ensure that when Zabbix asks for the database, it gets routed to the best available node from the 3 and moved to another node if that situation were to ever change.

I can connect via the MySQL client to the ProxySQL instance and run "SELECT VERSION();" which returns the expected MariaDB version (10.11.8), but when I point Zabbix to this same exact host/port, the service fails to start and the log reports a very different version number (I think it was 5.x something). And either way, setting AllowUnsupportedDBVersions=1 does not allow the service to start or bypass the database version compatibility error.

Also for confirmed compatibility, pointing our Zabbix server directly at one of the DB servers sitting behind ProxySQL runs with no issue.

[cyber]

5 minutes of google...
in your proxySQL config
SELECT * FROM global_variables ORDER BY variable_name;
you should see "mysql-server_version". update it to your "real" server version and you should be fine. I am pretty sure you find it is set to 5.5.30...

[HANDL_Eric]

5 minutes of google...
in your proxySQL config
SELECT * FROM global_variables ORDER BY variable_name;
you should see "mysql-server_version". update it to your "real" server version and you should be fine. I am pretty sure you find it is set to 5.5.30...

Thank you very much, i'll pass this along to the team. I'm still curious as to why the AllowUnsupportedDBVersions is Zabbix is no longer working.

[cyber]

Maybe just different places, which check the version.. somewhere in db query vs some library somewhere.. just a wild guess.