[MXS-2249] Using too big key for internal temp tables Created: 2019-01-08  Updated: 2019-01-09  Resolved: 2019-01-09

Status: Closed
Project: MariaDB MaxScale
Component/s: Authenticator
Affects Version/s: 2.2.18
Fix Version/s: N/A

Type: Bug Priority: Critical
Reporter: Cornillad Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Environment:

Centos 7
Maxscale version 2.2.18
DB version : MariaDB 10.3.2


Issue Links:
Duplicate
duplicates MXS-2209 Load users: Out of memory Closed

 Description   

Hi,

We have got many error when we restart our maxscale services

2019-01-08 20:36:59 error : [MySQLAuth] Failed to load users from server 'xx.xx.xx.xx': Internal error: Using too big key for internal temp tables

2019-01-08 20:36:59 notice : [MySQLAuth] [RWSVC] No users were loaded but 'inject_service_user' is enabled. Enabling service credentials for authentication until database users have been successfully loaded.

It begin with 10 or 15 warning per day, and for last few days we can't log into the database through maxscale.

Maxscale is able to telnet database server on port 3306, with maxscale account it can log in and show user database.

Direct access to database is okay with same account.

Not a network or a firewall problem.

Maxscale version 2.2.18
DB version : MariaDB 10.3.2

Could you help us ?

Thx



 Comments   
Comment by markus makela [ 2019-01-09 ]

This is a duplicate of MXS-2209 and is fixed in 2.2.19. It can be avoided by upgrading the MariaDB server or by using the server version faking feature described here: https://mariadb.com/kb/en/library/server-system-variables/#version

The error message in question is a possible outcome of MDEV-15840.

Generated at Thu Feb 08 04:12:45 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.