MySQL Bugs: #48239: Server crashing at irregular intervals

Bug #48239	Server crashing at irregular intervals
Submitted:	22 Oct 2009 17:58	Modified:	18 May 2010 2:50
Reporter:	Ed Macauley	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	5.1.37,5.1.44	OS:	Linux (Linux version 2.6.18-92.el5 (mockbuild@builder10.centos.org) (gcc version 4.1.2 20071124)
Assigned to:		CPU Architecture:	Any
Tags:	Signal 11, SSL

Description:
Getting repeated Signal 11 crashes.  Server runs fine for a random period of time and then crashes and restarts.  It appears to be related to yaSSL, may be related to Bug# 34236.

Most recent log entry w/ backtrace.  Will attach others:

091022 12:31:23 - mysqld got signal 11 ;
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=67108864
read_buffer_size=2097152
max_used_connections=30
max_threads=200
threads_connected=18
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 681971 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x2aab48312170
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 = 0x467e3f20 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x8496fe]
/usr/sbin/mysqld(handle_segfault+0x322)[0x5be9e2]
/lib64/libpthread.so.0[0x327e60de80]
/usr/sbin/mysqld(_ZNK5yaSSL11SSL_SESSION9GetBornOnEv+0x0)[0x87fc50]
/usr/sbin/mysqld(_ZN5yaSSL8Sessions5FlushEv+0x2d)[0x88426d]
/usr/sbin/mysqld(_ZN5yaSSL12sendFinishedERNS_3SSLENS_13ConnectionEndENS_12BufferOutputE+0x567)[0x88db37]
/usr/sbin/mysqld(yaSSL_accept+0x106)[0x873626]
/usr/sbin/mysqld[0x832022]
/usr/sbin/mysqld(handle_one_connection+0x308)[0x5c5548]
/lib64/libpthread.so.0[0x327e606307]
/lib64/libc.so.6(clone+0x6d)[0x327ded1ded]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at (nil) is an invalid pointer
thd->thread_id=101409
thd->killed=NOT_KILLED

How to repeat:
unknown

Suggested fix:
unknown

Log snippets w/ backtraces for bug #48239

Attachment: biglog.txt (text/plain), 8.12 KiB.

Thank you for the problem report. Do you use yaSSL or OpenSSL clients?

Sorry for the delay, we use OpenSSL 0.9.8b.  It's a PHP application on Apache.

We see the same problem.  5.1.39, CentOS 5.  We're making connections from the java MySQL Connector 5.1.6 and 5.1.10, with ?useSSL=true&requireSSL=true&verifyServerCertificate=false.  

We get these two stack traces:

stack_bottom = 0x448e4f10 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x84ac9e]
/usr/sbin/mysqld(handle_segfault+0x322)[0x5bf392]
/lib64/libpthread.so.0[0x3b48a0dd40]
/usr/sbin/mysqld(_ZN5mySTL7find_ifINS_4listIPN5yaSSL11SSL_SESSIONEE8iteratorENS2_20yassl_int_cpp_local210sess_matchEEET_S9_S9_T0_+0x32)[0x885e92]
/usr/sbin/mysqld(_ZN5yaSSL8Sessions6lookupEPKhPNS_11SSL_SESSIONE+0x30)[0x885670]
/usr/sbin/mysqld[0x8334f6]
/usr/sbin/mysqld(handle_one_connection+0x308)[0x5c5f58]
/lib64/libpthread.so.0[0x3b48a061b5]
/lib64/libc.so.6(clone+0x6d)[0x3b47ecd36d]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at (nil) is an invalid pointer
thd->thread_id=23645
thd->killed=NOT_KILLED

stack_bottom = 0x452d8f10 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x84ac9e]
/usr/sbin/mysqld(handle_segfault+0x322)[0x5bf392]
/lib64/libpthread.so.0[0x371460dd40]
/usr/sbin/mysqld(_ZNK5yaSSL11SSL_SESSION9GetBornOnEv+0x0)[0x8811f0]
/usr/sbin/mysqld(_ZN5yaSSL8Sessions5FlushEv+0x2d)[0x88580d]
/usr/sbin/mysqld(_ZN5yaSSL12sendFinishedERNS_3SSLENS_13ConnectionEndENS_12BufferOutputE+0x567)[0x88f0d7]
/usr/sbin/mysqld(yaSSL_accept+0x106)[0x874bc6]
/usr/sbin/mysqld[0x833512]
/usr/sbin/mysqld(handle_one_connection+0x308)[0x5c5f58]
/lib64/libpthread.so.0[0x37146061b5]
/lib64/libc.so.6(clone+0x6d)[0x3713acd36d]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at (nil) is an invalid pointer
thd->thread_id=272695
thd->killed=NOT_KILLED

confirmed on ubunutu 8.04
binary build

confirmed on
5.1.36
and 
5.1.44

100312  1:05:02 - mysqld got signal 11 ;
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=33554432
read_buffer_size=1048576
max_used_connections=154
max_threads=400
threads_connected=8
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 856039 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x3e853d50
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 = 0x45704110 thread_stack 0x30000
/opt/mysql/bin/mysqld(my_print_stacktrace+0x2e)[0x8afb6e]
/opt/mysql/bin/mysqld(handle_segfault+0x322)[0x5e12b2]
/lib/libpthread.so.0[0x7ff04c0687d0]
/opt/mysql/bin/mysqld(_ZNK5yaSSL11SSL_SESSION9GetBornOnEv+0x0)[0x8f4ae0]
/opt/mysql/bin/mysqld(_ZN5yaSSL8Sessions6lookupEPKhPNS_11SSL_SESSIONE+0x4b)[0x8f8fcb]
/opt/mysql/bin/mysqld(_ZN5yaSSL11ClientHello7ProcessERNS_12input_bufferERNS_3SSLE+0x2d3)[0x8f06f3]
/opt/mysql/bin/mysqld(_ZN5yaSSL15HandShakeHeader7ProcessERNS_12input_bufferERNS_3SSLE+0x122)[0x8f00d2]
/opt/mysql/bin/mysqld(_ZN5yaSSL14DoProcessReplyERNS_3SSLE+0x2e8)[0x9013e8]
/opt/mysql/bin/mysqld(_ZN5yaSSL12processReplyERNS_3SSLE+0x1d)[0x9015bd]
/opt/mysql/bin/mysqld(yaSSL_accept+0x58)[0x8e8068]
/opt/mysql/bin/mysqld[0x8961b0]
/opt/mysql/bin/mysqld[0x5eac9a]
/opt/mysql/bin/mysqld(handle_one_connection+0x151)[0x5eb2c1]
/lib/libpthread.so.0[0x7ff04c0603f7]
/lib/libc.so.6(clone+0x6d)[0x7ff04b4f9b4d]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at (nil) is an invalid pointer
thd->thread_id=357
thd->killed=NOT_KILLED

Just for information we also observe this bug in 5.1.44

Thank you for the feedback.

I can not repeat described behavior. Please provide more information about your application: configuration file, what kind of queries do you run. If it is possible to upload core file with mysqld to our FTP server please do it.

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".

Marking this bug a duplicate of bug #53287, see summary comment there.

Correction, duplicate of bug #34236 - see summary statement there