MySQL Bugs: #20196: intermittent YaSSL failures at replication

Bug #20196	intermittent YaSSL failures at replication
Submitted:	1 Jun 2006 12:19	Modified:	13 Aug 2007 9:00
Reporter:	Domas Mituzas	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	5.0.21	OS:	Linux (RHEL3, i686)
Assigned to:	Magnus Blåudd	CPU Architecture:	Any

Description:
YaSSL-encrypted replication sessions intermittently raise assertion failures:

060529 9:02:31 [Note] Slave I/O thread: connected to master '...:3306', replication started in log '...' at position ...
mysqld: buffer.cpp:41: void yaSSL::Check::check(unsigned int, unsigned int): Assertion `i < limit' failed.
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.
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.

Cannot determine thread, fp=0x665ca4, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x817a820
0xc957c8
(nil)
0xa8adb1
0x83ee406
0x83ee75a
0x83e54b5
0x83f5de3
0x83f60f6
0x83f6ad2
0x83df9be
0x83a31eb
0x8173333
0x8173693
0x826467c
0x825c6fd
0x825d2d4
0xc8f341
0xb316fe
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at (nil) is invalid pointer
thd->thread_id=115
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.

Number of processes running now: 0
060529 09:30:51 mysqld restarted

How to repeat:
n/a

Suggested fix:
Abort sessions rather than crash on SSL failures.

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

I'm running 5.0.22 (installed via RPM) on a Fedora Core 3 system and am getting this very same error.  Is there a fix yet?  After all the problems I've experienced with MySQL Replication and SSL, my boss is going to kill me if I can't get this working as soon as possible.

I upgraded our slave MySQL server to the 5.0.24 RPM's and that solved this problem for me.  The master MySQL server is still running with 5.0.22, but I'll be upgrading that soon as well.

Troy,

thank you for the feedback. Status of the report has been updated because your comment.