[MDEV-14863] Startup fails with "can't write lock OpenSSL lock" Created: 2018-01-03  Updated: 2018-08-31  Resolved: 2018-08-31

Status: Closed
Project: MariaDB Server
Component/s: Server
Affects Version/s: 10.1.25
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Geoff Montee (Inactive) Assignee: Sergei Golubchik
Resolution: Duplicate Votes: 0
Labels: crash, openssl, startup

Issue Links:
Duplicate
is duplicated by MDEV-14343 Server crash on FIPS with openssl-1.0.2k Closed

 Description   

A server recently began to fail at startup with the following error:

2018-01-02 14:01:29 139623385635072 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-01-02 14:01:29 139623385635072 [Note] InnoDB: The InnoDB memory heap is disabled
2018-01-02 14:01:29 139623385635072 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-01-02 14:01:29 139623385635072 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2018-01-02 14:01:29 139623385635072 [Note] InnoDB: Compressed tables use zlib 1.2.7
2018-01-02 14:01:29 139623385635072 [Note] InnoDB: Using Linux native AIO
2018-01-02 14:01:29 139623385635072 [Note] InnoDB: Using SSE crc32 instructions
2018-01-02 14:01:29 139623385635072 [Note] InnoDB: Initializing buffer pool, size = 16.0G
2018-01-02 14:01:29 139623385635072 [Note] InnoDB: Completed initialization of buffer pool
2018-01-02 14:01:29 139623385635072 [ERROR] Fatal: can't write lock OpenSSL lock
180102 14:01:29 [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.1.25-MariaDB
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=0
max_threads=302
thread_count=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 485165 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 0x48400
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55ca81e5f36e]
/usr/sbin/mysqld(handle_fatal_signal+0x305)[0x55ca81987245]
/lib64/libpthread.so.0(+0xf5e0)[0x7efc9a0f05e0]
/lib64/libc.so.6(gsignal+0x37)[0x7efc983c91f7]
/lib64/libc.so.6(abort+0x148)[0x7efc983ca8e8]
/usr/sbin/mysqld(+0x39a63f)[0x55ca8176a63f]
mysys/stacktrace.c:268(my_print_stacktrace)[0x7efc9908b96d]
sql/mysqld.cc:4702(openssl_lock_function(int, int, char const*, int))[0x7efc9908c469]
/lib64/libcrypto.so.10(ssleay_rand_bytes+0xe6)[0x7efc9908b076]
mysys_ssl/my_crypt.cc:315(my_random_bytes)[0x55ca81e75170]
include/sync0sync.ic:535(fil_space_create_crypt_data(unsigned int, fil_encryption_t, unsigned int, unsigned int) [clone .constprop.37])[0x55ca81dcf2f4]
fil/fil0crypt.cc:354(fil_space_read_crypt_data(unsigned long, unsigned char const*, unsigned long))[0x55ca81dd0429]
fil/fil0fil.cc:2453(fil_read_first_page(pfs_os_file_t, unsigned long, unsigned long*, unsigned long*, unsigned long*, fil_space_crypt_t**))[0x55ca81dc24c3]
srv/srv0start.cc:1134(open_or_create_data_files(bool*, unsigned long*, unsigned long*, unsigned long*, unsigned long*))[0x55ca81cf6d26]
srv/srv0start.cc:2276(innobase_start_or_create_for_mysql())[0x55ca81cf8c72]
handler/ha_innodb.cc:4454(innobase_init(void*))[0x55ca81c1a80d]
sql/handler.cc:513(ha_initialize_handlerton(st_plugin_int*))[0x55ca819894e4]
sql/sql_plugin.cc:1406(plugin_initialize(st_mem_root*, st_plugin_int*, int*, char**, bool))[0x55ca818168c0]
sql/sql_plugin.cc:1683(plugin_init(int*, char**, int))[0x55ca8181815a]
sql/mysqld.cc:5148(init_server_components())[0x55ca817705d8]
sql/mysqld.cc:5737(mysqld_main(int, char**))[0x55ca81773f10]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7efc983b5c05]
/usr/sbin/mysqld(+0x397e7d)[0x55ca81767e7d]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

This error started after the user enabled FIPS mode in RHEL 7, but I don't know if that is relevant.



 Comments   
Comment by Elena Stepanova [ 2018-01-03 ]

It looks remarkably similar to MDEV-14343.

Generated at Thu Feb 08 08:16:52 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.