[MDEV-11980] libgalera_smm.so: undefined symbol: SSLv2_method Created: 2017-02-02  Updated: 2017-09-15  Resolved: 2017-06-29

Status: Closed
Project: MariaDB Server
Component/s: Galera
Affects Version/s: 10.1.21
Fix Version/s: 10.1.24

Type: Bug Priority: Critical
Reporter: John Bonds Assignee: Sachin Setiya (Inactive)
Resolution: Fixed Votes: 1
Labels: None
Environment:

Ubuntu Xenial 16.04


Sprint: 10.1.23

 Description   

Ubuntu apparently uses a version of libssl that doesn't have SSLv2 and for some reason libgalera_smm.so needs it. When I try to bootstrap a cluster I see the following in my logs:
libgalera_smm.so: undefined symbol: SSLv2_method

2017-02-02 13:06:28 140394012358528 [ERROR] WSREP: wsrep_load(): dlopen(): /opt/mysql/home/lib/galera/libgalera_smm.so: undefined symbol: SSLv2_method
2017-02-02 13:06:28 140394012358528 [ERROR] WSREP: wsrep_load(/opt/mysql/home/lib/galera/libgalera_smm.so) failed: Invalid argument (22). Reverting to no provider.



 Comments   
Comment by Daniel Black [ 2017-02-26 ]

It seems your galera version isn't distributed by mariadb.

Galera have corrected this error in their 25.3.19/20 releases.
https://github.com/codership/galera/commit/153ff782d7b3ace6eaa0dae3c0153c7f7328a1c8

Alternately using the galera-3 package from Ubuntu will probably not have this fault (no bugs listed).
http://packages.ubuntu.com/xenial/galera-3

If you believe this is still a problem please provide details as to how you got /opt/mysql/home/lib/galera/libgalera_smm.so and what version it is.

Comment by Nilnandan Joshi [ 2017-03-21 ]

All RPMs has this issue. Yes, it can be resolved installing Galera-3 and point path there for ibgalera_smm.so file.

Comment by Andrii Nikitin (Inactive) [ 2017-03-21 ]

Apparently Galera from official MariaDB 10.1.22 .tar.gz doesn't work because of this problem on Ubuntu 16.04

Comment by John Bonds [ 2017-03-21 ]

From what I remember, the issue was solved by installing openssl. Not sure why it wasn't already installed or updated.

Comment by Patrick Rono [ 2017-09-15 ]

Got the same error on 10.1.24

Generated at Thu Feb 08 07:54:09 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.