Bug #53287 The mysql server crashed if SSL is used.
Submitted: 29 Apr 2010 14:47 Modified: 18 May 2010 2:50
Reporter: Dmitry Kolesnik Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.1.46 OS:Windows (Server 2008)
Assigned to: CPU Architecture:Any

[29 Apr 2010 14:47] Dmitry Kolesnik
Description:
I have installed MySQL server 5.1.46 on Windows Server 2008.
The SSL cert is used for this instance. SSL works fine. But some times server crashes with exception 

100429 15:00:01 - mysqld got exception 0xc0000005 ;
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.
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.

key_buffer_size=209715200
read_buffer_size=2097152
max_used_connections=27
max_threads=10000
threads_connected=14
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1958544 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x3a5e2420
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...
00000001403578F0    mysqld.exe!yaSSL::SSL_SESSION::GetBornOn()[yassl_int.cpp:1522]
000000014035C8A3    mysqld.exe!yaSSL::Sessions::lookup()[yassl_int.cpp:1659]
0000000140360799    mysqld.exe!yaSSL::ClientHello::Process()[yassl_imp.cpp:1544]
0000000140362052    mysqld.exe!yaSSL::HandShakeHeader::Process()[yassl_imp.cpp:666]
0000000140365C84    mysqld.exe!yaSSL::DoProcessReply()[handshake.cpp:778]
0000000140365DBA    mysqld.exe!yaSSL::processReply()[handshake.cpp:792]
000000014034EEE4    mysqld.exe!yaSSL_accept()[ssl.cpp:337]
000000014038481A    mysqld.exe!ssl_do()[viossl.c:205]
00000001400981EF    mysqld.exe!check_connection()[sql_connect.cc:805]
00000001400984BE    mysqld.exe!login_connection()[sql_connect.cc:956]
0000000140098627    mysqld.exe!handle_one_connection()[sql_connect.cc:1119]
000000014031BB65    mysqld.exe!pthread_start()[my_winthread.c:85]
00000001402E5C17    mysqld.exe!_callthreadstart()[thread.c:295]
00000001402E5CE5    mysqld.exe!_threadstart()[thread.c:275]
00000000774EBE3D    kernel32.dll!BaseThreadInitThunk()
0000000077626A51    ntdll.dll!RtlUserThreadStart()
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0000000000000000=(null)
thd->thread_id=698
thd->killed=NOT_KILLED
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.
100429 15:05:02 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
100429 15:05:09  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...

This happens 2-3 times per day. 

The SSL was generated with using instruction http://dev.mysql.com/doc/refman/5.0/en/secure-create-certs.html.  

[mysqld]
ssl-key=C:/OpenSSL/bin/server-key.pem
ssl-cert=C:/OpenSSL/bin/server-cert.pem
ssl-ca=C:/OpenSSL/bin/ca-cert.pem

How to repeat:
Use SSL for MySQL server. It seems that issue happens at opening SSL connections with MySQL server, but this happens not for each connections.
[29 Apr 2010 14:49] Dmitry Kolesnik
Ini file

Attachment: my.ini (application/octet-stream, text), 3.26 KiB.

[29 Apr 2010 14:51] Dmitry Kolesnik
Error file

Attachment: ip-0AD15DAB.err (application/octet-stream, text), 34.54 KiB.

[18 May 2010 2:50] Roel Van de Paar
Marking this bug a duplicate of bug #53287, see summary comment there.
[26 May 2010 11:03] Hartmut Holzgraefe
actually a duplicate of bug #34236