[MXS-3584] Invalid authentication message 'Unknown command' when persistent connections are used Created: 2021-06-01 Updated: 2021-08-02 Resolved: 2021-08-02 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Core |
| Affects Version/s: | 2.5.11 |
| Fix Version/s: | 2.5.14 |
| Type: | Bug | Priority: | Major |
| Reporter: | Alex | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Debian buster. Backend 10.4.19, 10.5.10 |
||
| Sprint: | MXS-SPRINT-133 |
| Description |
|
In the logs:
|
| Comments |
| Comment by Alex [ 2021-06-01 ] |
|
Config: |
| Comment by Alex [ 2021-06-01 ] |
|
Using this lib to connect: https://www.npmjs.com/package/mysql2 |
| Comment by markus makela [ 2021-06-01 ] |
|
Is this with or without persistent connections in MaxScale? |
| Comment by Alex [ 2021-06-01 ] |
|
Between MaxScale and Backend or Application and Maxscale? |
| Comment by markus makela [ 2021-06-01 ] |
|
MaxScale and the backend database servers. |
| Comment by Alex [ 2021-06-01 ] |
|
yes. persitent connections enabled |
| Comment by Alex [ 2021-06-03 ] |
|
I've set persistpoolmax=0 for all backends and the problem has disapeared. |
| Comment by markus makela [ 2021-06-03 ] |
|
Thanks for confirming, I think this and |
| Comment by markus makela [ 2021-06-21 ] |
|
Once we release MaxScale 2.5.14, please try and see if this now works with persistent connections. If it does, then this is likely the same problem that was in |
| Comment by Kester Riley [ 2021-06-21 ] |
|
Please note I am having this issue with MaxScale 2.5.13 with one of my customers currently as well. |
| Comment by markus makela [ 2021-07-23 ] |
|
alexcool now that 2.5.14 is out, would it be possible for you to re-test and see if this still occurs? |
| Comment by markus makela [ 2021-08-02 ] |
|
Closing as Fixed until, it's highly likely that this is fixed by the other fixes in 2.5.14. If this bug still happens with 2.5.14, please let us know and we'll reopen it. |