[MXS-2961] Connection fails with ssl=true and MariaDB 10.1.44 Created: 2020-04-12 Updated: 2020-08-20 Resolved: 2020-08-20 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Authenticator, mariadbbackend |
| Affects Version/s: | 2.4.8 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Oy5p aegh | Assignee: | markus makela |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Debian 10 (Buster) |
||
| Description |
|
When enabling ssl=true the connection to MariaDB 10.1.44 fails with error:
|
| Comments |
| Comment by markus makela [ 2020-04-14 ] |
|
Looks like it might be a TLS protocol version issue, try adding ssl_version=TLSv11 or ssl_version=TLSv10 and see if that works. What OS is the database running on? |
| Comment by Oy5p aegh [ 2020-04-14 ] |
|
After adding ssl_version=TLSv11 (TLSv10 is not available) the same behavior shows: MaxScale failed to connect with error 2026. |
| Comment by markus makela [ 2020-04-24 ] |
|
I apologize, the error is not from a client connection but an internal maxscale connection. This would mean it's related to the C connector configuration that we use. |
| Comment by markus makela [ 2020-07-03 ] |
|
It's possible that the version of connector C we use and the protocols supported by MariaDB 10.1 are not compatible. Can you reproduce this with a newer MariaDB release (10.1 is EOL)? |
| Comment by markus makela [ 2020-08-20 ] |
|
We haven't been able to reproduce this and 10.1 is no longer supported. |