Zabbix-Server on startup will check whether the sql server version is supported or not.
Therefore Zabbix uses the version from reported by php's mysql_get_server_info function which sometimes e.g. when using proxysql won't be the actual sql server version.
Example on Proxysql2 (from Percona):
mysql -u zabbix -p -P 6033 -h 10.10.10.10
Server version: 5.5.30 (ProxySQL) <-- Zabbix complains about at too old sql server version
mysql> select @@version;
+-------------+
| @@version |
+-------------+
| 8.0.32-24.1 | <-- Real MySQL/MariaDB backend server version
+-------------+
This will e.g. lead to following error:
Unable to start Zabbix server due to unsupported MySQL database version (5.05.30).
Must be at least (8.00.30).
Suggest to check the "actual" sql server version by "select @@version;" and not by the php built in function on /zabbix/src/libs/zbxdb/db.c lines 2672 to 2730.
Therefore Zabbix uses the version from reported by php's mysql_get_server_info function which sometimes e.g. when using proxysql won't be the actual sql server version.
Example on Proxysql2 (from Percona):
mysql -u zabbix -p -P 6033 -h 10.10.10.10
Server version: 5.5.30 (ProxySQL) <-- Zabbix complains about at too old sql server version
mysql> select @@version;
+-------------+
| @@version |
+-------------+
| 8.0.32-24.1 | <-- Real MySQL/MariaDB backend server version
+-------------+
This will e.g. lead to following error:
Unable to start Zabbix server due to unsupported MySQL database version (5.05.30).
Must be at least (8.00.30).
Suggest to check the "actual" sql server version by "select @@version;" and not by the php built in function on /zabbix/src/libs/zbxdb/db.c lines 2672 to 2730.