Maxscale 2.2.21 version does not work with Mariadb 10.5, 10.6 version
There is no problem when linking with mariadb 10.4 When linking with version 10.5 or later, a symptom of not being able to connect to Mariadb occurs.
Check the normal operation in maxscale 2.3 version
What should I change in maxscale 2.2 version to make the authentication work properly?
At the bottom are the server options and logs.
maxscale - maxscale.cnf
[server1] type=server address=10.178.0.9 port=3306 protocol=MariaDBBackend
[MariaDB-Monitor] type=monitor module=mariadbmon servers=server1 user=maxscale passwd=maxscale_pw monitor_interval=2000
[Read-Write-Service] type=service router=readwritesplit servers=server1 user=maxscale passwd=maxscale_pw
maxscale - log [MariaDB-Monitor] Failed to connect to server 'server1' ([10.178.0.9]:3306) when checking monitor user credentials and permissions: Lost connection to MySQL server during query [MariaDB-Monitor] Failed to connect to server 'server1' ([10.178.0.9]:3306) when checking monitor user credentials and permissions: Lost connection to MySQL server during query
mariadb - error.log [Warning] Aborted connection 52 to db: 'unconnected' user: 'maxscale' host: 'xxxx' (Got an error reading communication packets) mariadb - general.log Connect maxscale@xxxx on using TCP/IP
Answer Answered by Markus Mäkelä in this comment.
MariaDB 10.5 was released after the MaxScale 2.2 EOL date of January 1st 2020 which means support for it was not built into it. The reason for this is most likely some change in how the communication between MaxScale 2.2 and MariaDB 10.5 is done which was added or fixed for MaxScale 2.3.
Since MaxScale 2.3 is EOL as well (as of January 2022), I'd recommend using a newer version of MaxScale, if possible.