MySQL Bugs: #84690: MySQL crashes on startup with existing ssl-certificates on Nano Server

Bug #84690	MySQL crashes on startup with existing ssl-certificates on Nano Server
Submitted:	27 Jan 2017 8:05	Modified:	2 May 2018 14:22
Reporter:	Sebastian Tkaczuk	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	5.7.17	OS:	Windows (Nano Server 2016 (64bit))
Assigned to:		CPU Architecture:	Any
Tags:	64bit, cert, crash, SSL

Description:
Deploying MySQL 5.7.17 (5.7.9 also testes) on Nano Server works.
OpenSSL on nano-server also working.

Without existing ssl-certificates mysqld starts as expected.
With existing ssl-certificates (after calling mysql_ssl_rsa_setup) mysql crashes.

Command mysqld --console shows following error:

mysqld : 2017-01-27T07:57:12.143150Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use 
--explicit_defaults_for_timestamp server option (see documentation for more details).
    + CategoryInfo          : NotSpecified: (2017-01-27T07:5... more details).:String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError
 
2017-01-27T07:57:12.143150Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are 
disabled
2017-01-27T07:57:12.143150Z 0 [Note] C:\MySQL\mysql\bin\mysqld.exe (mysqld 5.7.17) starting as process 1156 ...
2017-01-27T07:57:12.158776Z 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-01-27T07:57:12.158776Z 0 [Note] InnoDB: Uses event mutexes
2017-01-27T07:57:12.158776Z 0 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-01-27T07:57:12.158776Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-01-27T07:57:12.158776Z 0 [Note] InnoDB: Number of pools: 1
2017-01-27T07:57:12.158776Z 0 [Note] InnoDB: Not using CPU crc32 instructions
2017-01-27T07:57:12.158776Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2017-01-27T07:57:12.174400Z 0 [Note] InnoDB: Completed initialization of buffer pool
2017-01-27T07:57:12.268221Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2017-01-27T07:57:12.299443Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 2535954
2017-01-27T07:57:12.299443Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 2535963
2017-01-27T07:57:12.315095Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 2535963
2017-01-27T07:57:12.315095Z 0 [Note] InnoDB: Database was not shutdown normally!
2017-01-27T07:57:12.315095Z 0 [Note] InnoDB: Starting crash recovery.
2017-01-27T07:57:12.796366Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2017-01-27T07:57:12.796366Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2017-01-27T07:57:12.796366Z 0 [Note] InnoDB: Setting file '.\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2017-01-27T07:57:12.918427Z 0 [Note] InnoDB: File '.\ibtmp1' size is now 12 MB.
2017-01-27T07:57:12.918427Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2017-01-27T07:57:12.918427Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2017-01-27T07:57:12.918427Z 0 [Note] InnoDB: Waiting for purge to start
2017-01-27T07:57:12.996104Z 0 [Note] InnoDB: 5.7.17 started; log sequence number 2535963
2017-01-27T07:57:12.996104Z 0 [Note] Plugin 'FEDERATED' is disabled.
2017-01-27T07:57:12.996104Z 0 [Note] InnoDB: Loading buffer pool(s) from C:\MySQL\mysql\data\ib_buffer_pool
2017-01-27T07:57:13.122336Z 0 [Note] Found ca.pem, server-cert.pem and server-key.pem in data directory. Trying to enable SSL 
support using them.
2017-01-27T07:57:13.122336Z 0 [Warning] CA certificate ca.pem is self signed.
07:57:13 UTC - mysqld got exception 0xc000001d ;
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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68011 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...
2017-01-27T07:57:13.372261Z 0 [Note] InnoDB: Buffer pool(s) load completed at 170127  8:57:13
7ff660d53343    
mysqld.exe!log()[log.asm:429]
7ff660d22cbc    
mysqld.exe!TaoCrypt::`anonymous namespace'::DiscreteLogWorkFactor()[dh.cpp:40]
7ff660d22d9b    
mysqld.exe!TaoCrypt::DH::GeneratePrivate()[dh.cpp:58]
7ff660d22d2d    
mysqld.exe!TaoCrypt::DH::GenerateKeyPair()[dh.cpp:50]
7ff660d05704    
mysqld.exe!yaSSL::DiffieHellman::DiffieHellman()[crypto_wrapper.cpp:830]
7ff660cf6a27    
mysqld.exe!yaSSL::Crypto::SetDH()[yassl_int.cpp:2389]
7ff660cf4db2    
mysqld.exe!yaSSL::SSL::SSL()[yassl_int.cpp:414]
7ff6602418db    
mysqld.exe!init_ssl()[mysqld.cc:3441]
7ff6602462b8    
mysqld.exe!win_main()[mysqld.cc:4834]
7ff660243865    
mysqld.exe!mysql_service()[mysqld.cc:5123]
7ff660243c1c    
mysqld.exe!mysqld_main()[mysqld.cc:5321]
7ff660d4c630    
mysqld.exe!__tmainCRTStartup()[crt0.c:255]
7ffc072b70df    
ntdll.dll!RtlUserThreadStart()
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.

How to repeat:
First: Deploy mysql on nano server.
Description here: https://ryentang.wordpress.com/2016/06/28/nano-server-deploying-mysql-database-server/

Test mysqld. It should work.

Call mysql_ssl_rsa_setup.

Test mysqld again. It should crash.

Going to guess this is the same as mine (log function uses vpsrlq ask instruction) that isn't supported on hardware or OS version:

https://bugs.mysql.com/bug.php?id=81197

MySQL not only crashing with existing ssl-certificates.
Also during operations, mysql crashes on nano server.
Error log shows:

13:15:03 UTC - mysqld got exception 0xc000001d ;
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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=27
max_threads=151
thread_count=23
connection_count=23
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68011 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x19994b91770
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...
7ff744872571    mysqld.exe!pow()[pow.asm:1616]
7ff743d8da3a    mysqld.exe!get_sweep_read_cost()[handler.cc:7200]
7ff74434f3a7    mysqld.exe!ror_intersect_add()[opt_range.cc:5440]
7ff7443453a9    mysqld.exe!get_best_ror_intersect()[opt_range.cc:5621]

WORKAROUND using Hyper-V 2012 R2:
For virtual nano machine activate processor compatibility-mode for porting to another machine.
Seems to work for now...

It's already an issue or was solver like https://bugs.mysql.com/bug.php?id=81197?. Thanks.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".