The Ultimate Guide to High Availability with MariaDB

Comments - start the first cluster node failed with libssl.so.6 problem

8 years, 3 months ago Yu Denis
Re: start the first cluster node failed with libssl.so.6 problem [Answer]

I don't have root or sudo access for the server i worked on for galera, but it pretty much same as following server. which i have root access ( we have standard redhat 6 env for all the linux server in our company):

root@xxx:/root # ldconfig -p | grep 'libssl\|libcrypto'
        libssl3.so (libc6,x86-64) => /usr/lib64/libssl3.so
        libssl.so.10 (libc6,x86-64) => /usr/lib64/libssl.so.10
        libcrypto.so.10 (libc6,x86-64) => /usr/lib64/libcrypto.so.10

btw in the above server (EL6) that i have root access,i created soft link libssl.so.6 and libcrypto.so.6,

fxxxxx02:/usr/lib64$ ls -l libssl.so.6
lrwxrwxrwx 1 root root 16 Jan  4 14:23 libssl.so.6 -> libssl.so.1.0.1e
fxxxx02:/usr/lib64$ ls -l libcrypto.so.6
lrwxrwxrwx 1 root root 19 Jan  4 14:24 libcrypto.so.6 -> libcrypto.so.1.0.1e

It seems i can bring up the first node by that way.I am not sure if it really works or not, as I am waiting for SA to create similar links for bunch of servers that i will test the galera cluster.

Denis

 
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.