mariadb-10.2.24-linux-glibc_214-x86_64.tar.gz

MariaDB Start AND Crash

2019-05-23 12:24:00 139758071879488 [Note] WSREP: Read nil XID from storage engines, skipping position init
2019-05-23 12:24:00 139758071879488 [Note] WSREP: wsrep_load(): loading provider library '/app/mariadb/mariadb/lib/galera/libgalera_smm.so'
2019-05-23 12:24:00 139758071879488 [ERROR] WSREP: wsrep_load(): dlopen(): /app/mariadb/mariadb/lib/galera/libgalera_smm.so: symbol ERR_remove_thread_state, version OPENSSL_1.0.0 not defined in file libcrypto.so.1.0.0 with link time reference
2019-05-23 12:24:00 139758071879488 [ERROR] WSREP: wsrep_load(/app/mariadb/mariadb/lib/galera/libgalera_smm.so) failed: Invalid argument (22). Reverting to no provider.
2019-05-23 12:24:00 139758071879488 [Note] WSREP: Read nil XID from storage engines, skipping position init
2019-05-23 12:24:00 139758071879488 [Note] WSREP: wsrep_load(): loading provider library 'none'
2019-05-23 12:24:00 139758071879488 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-05-23 12:24:00 139758071879488 [Note] InnoDB: Uses event mutexes
2019-05-23 12:24:00 139758071879488 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-05-23 12:24:00 139758071879488 [Note] InnoDB: Using Linux native AIO
2019-05-23 12:24:00 139758071879488 [Note] InnoDB: Number of pools: 1
2019-05-23 12:24:00 139758071879488 [Note] InnoDB: Using SSE2 crc32 instructions
2019-05-23 12:24:00 139758071879488 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2019-05-23 12:24:00 139758071879488 [Note] InnoDB: Completed initialization of buffer pool
2019-05-23 12:24:00 139757318100736 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-05-23 12:24:00 139758071879488 [Note] InnoDB: Highest supported file format is Barracuda.
2019-05-23 12:24:00 139758071879488 [Note] InnoDB: 128 out of 128 rollback segments are active.
190523 12:24:00 [ERROR] mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 10.2.24-MariaDB-log
key_buffer_size=67108864
read_buffer_size=2097152
max_used_connections=0
max_threads=1025
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 4285789 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0x0 thread_stack 0x49000