-
Notifications
You must be signed in to change notification settings - Fork 176
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Galera-4 (26.4.16) not working with MariaDB 11.0.5 or 11.1.4 when using socket.ssl_cipher #656
Comments
@klau2005 I ran into this same issue.. Have you figured it out, or are you still waiting for a response? FWI: I filed a bug-report and MariaDB too: https://jira.mariadb.org/browse/MDEV-34738 |
Hi @tvdijen , |
Thanks! I'll keep you posted on activity at MariaDB |
Hi, Have you opened MDEV for MariaDB. At least 11.4 this could be related to new ssl feature. |
|
We are running a 3 node Galera cluster, each node running MariaDB 10.11.7 on Ubuntu 22.04. Both Galera and MariaDB were installed via apt from the official repositories. The cluster is configured with SSL for both server and replication traffic. Below an excerpt of the Galera configuration file related to WSREP and SSL:
This setup works perfect with the above versions. After upgrading one node to MariaDB 11.0.5 or 11.1.4, that node fails to start and the error in the log is:
I tried to restrict that list to only one cipher in the hope that maybe it somehow stopped wanting all the ciphers listed in there. Same error. Only when I removed the parameter completely did the error go away. However, that is not what we want as we have to have SSL enabled for the replication traffic.
The text was updated successfully, but these errors were encountered: