Bug #73020 MySQL crash whilst running mysqldump
Submitted: 17 Jun 2014 9:48 Modified: 18 Jul 2014 18:05
Reporter: David Vaughan Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: General Severity:S3 (Non-critical)
Version:5.5.33-cll-lve OS:Linux (RHEL 6.4)
Assigned to: CPU Architecture:Any
Tags: crash, mysqldump

[17 Jun 2014 9:48] David Vaughan
Description:
MySQL crashed last night with no apparent error. I'm not sure if it was related but the nightly mysqldump was running at the time. See below for stack trace:

pure virtual method called
terminate called without an active exception
04:15:02 UTC - 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.

key_buffer_size=402653184
read_buffer_size=262144
max_used_connections=300
max_threads=800
thread_count=38
connection_count=38
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2245822 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x165b14e0
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 = 7f6d3abd3d98 thread_stack 0x40000
/usr/libexec/mysqld(my_print_stacktrace+0x2e)[0x78f67e]
/usr/libexec/mysqld(handle_fatal_signal+0x493)[0x678443]
/lib64/libpthread.so.0[0x30bf20f500]
/lib64/libc.so.6(gsignal+0x35)[0x30bee328e5]
/lib64/libc.so.6(abort+0x175)[0x30bee340c5]
/usr/lib64/libstdc++.so.6(_ZN9__gnu_cxx27__verbose_terminate_handlerEv+0x12d)[0x3dd44bea5d]
/usr/lib64/libstdc++.so.6[0x3dd44bcbe6]
/usr/lib64/libstdc++.so.6[0x3dd44bcc13]
/usr/lib64/libstdc++.so.6[0x3dd44bd53f]
/usr/libexec/mysqld(_ZN9Log_event12write_headerEP11st_io_cachem+0x82)[0x712f92]
/usr/libexec/mysqld(_ZN9Log_event5writeEP11st_io_cache+0x28)[0x533598]
/usr/libexec/mysqld(_ZN13MYSQL_BIN_LOG4openEPKc13enum_log_typeS1_10cache_typebmbb+0x2db)[0x7032db]
/usr/libexec/mysqld(_ZN13MYSQL_BIN_LOG13new_file_implEb+0x468)[0x704bc8]
/usr/libexec/mysqld(_Z16rotate_relay_logP11Master_info+0x24)[0x5289e4]
/usr/libexec/mysqld(_Z20reload_acl_and_cacheP3THDmP10TABLE_LISTPi+0x41a)[0x63ac9a]
/usr/libexec/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0xa3a)[0x5894ba]
/usr/libexec/mysqld(_Z24do_handle_one_connectionP3THD+0xda)[0x61d1da]
/usr/libexec/mysqld(handle_one_connection+0x5b)[0x61d31b]
/lib64/libpthread.so.0[0x30bf207851]
/lib64/libc.so.6(clone+0x6d)[0x30beee894d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 42935555
Status: 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.
140617 05:15:03 mysqld_safe Number of processes running now: 0
140617 05:15:03 mysqld_safe mysqld restarted

How to repeat:
Unknown at present.
[18 Jun 2014 18:05] MySQL Verification Team
Please try 5.5.38 http://dev.mysql.com/downloads/mysql/5.5.html#downloads. Thanks.
[19 Jul 2014 1:00] Bugs System
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".