Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
2.5.5
-
None
-
MXS-SPRINT-121
Description
A lot of errors are logged after upgrading to 2.5.5 (from 2.3.x)
MariaDB version is 10.3.25
2020-11-01 16:30:24 error : (511660) Invalid authentication message from backend 'db3'. Error code: 1047, Msg : #08S01: Unknown command |
2020-11-01 16:30:24 error : (511660) Invalid authentication message from backend 'db2'. Error code: 1047, Msg : #08S01: Unknown command |
2020-11-01 16:30:25 error : (511660) Invalid authentication message from backend 'db3'. Error code: 1047, Msg : #08S01: Unknown command |
2020-11-01 16:30:42 error : (512393) Invalid authentication message from backend 'db3'. Error code: 1047, Msg : #08S01: Unknown command |
2020-11-01 16:30:42 error : (512393) Invalid authentication message from backend 'db2'. Error code: 1047, Msg : #08S01: Unknown command |
2020-11-01 16:30:43 error : (512393) Invalid authentication message from backend 'db3'. Error code: 1047, Msg : #08S01: Unknown command |
2020-11-01 16:30:47 error : (512527) Invalid authentication message from backend 'db2'. Error code: 1047, Msg : #08S01: Unknown command |
2020-11-01 16:30:47 error : (512527) Invalid authentication message from backend 'db3'. Error code: 1047, Msg : #08S01: Unknown command |
2020-11-01 16:31:02 error : (513425) Invalid authentication message from backend 'db3'. Error code: 1047, Msg : #08S01: Unknown command |
2020-11-01 16:31:02 error : (513425) Invalid authentication message from backend 'db2'. Error code: 1047, Msg : #08S01: Unknown command |
2020-11-01 16:31:02 error : (513426) Invalid authentication message from backend 'db3'. Error code: 1047, Msg : #08S01: Unknown command |
2020-11-01 16:31:02 error : (513429) Invalid authentication message from backend 'db3'. Error code: 1047, Msg : #08S01: Unknown command |
2020-11-01 16:31:02 error : (513426) Invalid authentication message from backend 'db2'. Error code: 1047, Msg : #08S01: Unknown command |
I have virtually no clue why I'm getting these, most connections seem to work fine.
Attachments
Activity
persistent_connections is the current pool size (a bit of an unfortunate name for the field, should've been current_pool_size) and max_pool_size is the maximum number ever reached. The latter should eventually be the same value as persistpoolmax in the configuration file.
then how can max_pool_size < persistent_connections ? or am i missing something
I missed that part and it definitely looks strange: I think the pool maximum might be for a single thread and the total count might be for all the threads. If you can, could you open a separate bug report for this?
I'll close this as Fixed in 2.5.9 since you haven't seen any problems with that release. If you see any problems, let us know and we'll reopen this.
about those last two, persistent_connections is a static number and max_pool_size the current available?