Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
2.3.13, 2.4.2
-
None
Description
If the WITH RECURSIVE query reading user privileges and passwords takes longer than a second, the connection running the query is terminated and none of the mysqld users get known to maxscale.
On the maxscale size things fail with
Nov 08 23:28:39 maxscale maxscale[3249]: Failed to load users from server 'server1': Lost connection to MySQL server during query
|
Nov 08 23:28:39 maxscale maxscale[3249]: Added user: INSERT OR REPLACE INTO mysqlauth_users VALUES ('maxscale', '%', NULL, 1, '14E65567ABDB5135D0CFD9A70B3032C179A49EE7')
|
Nov 08 23:28:39 maxscale maxscale[3249]: Added user: INSERT OR REPLACE INTO mysqlauth_users VALUES ('maxscale', 'localhost', NULL, 1, '14E65567ABDB5135D0CFD9A70B3032C179A49EE7')
|
Nov 08 23:28:39 maxscale maxscale[3249]: [Read-Write-Service] No users were loaded but 'inject_service_user' is enabled. Enabling service credentials for authentication until database users have been successfully loaded.
|
Nov 08 23:28:39 maxscale maxscale[3249]: [MySQLAuth] Read-Write-Service: login attempt for user 'foo2'@[127.0.0.1]:35828, authentication failed. User not found.
|
On the MariaDB server side there are just two reports about aborted connections
Nov 08 23:28:38 node-1 mysqld[4888]: 2019-11-08 23:28:38 120 [Warning] Aborted connection 120 to db: 'mysql' user: 'maxscale' host: 'maxscale' (Got an error writing communication packets)
|
Nov 08 23:28:39 node-1 mysqld[4888]: 2019-11-08 23:28:39 121 [Warning] Aborted connection 121 to db: 'mysql' user: 'maxscale' host: 'maxscale' (Got an error writing communication packets)
|
Attachments
Issue Links
- relates to
-
-
- Closed
-