It seems same problem still happens on the intermediate master with 5.5.48-37.8 when FLUSH LOGS is executed there on regular basis to get a chance to save/sync binary logs:
pure virtual method called
terminate called without an active exception
22:40:01 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.
Please help us make Percona Server better by reporting any
bugs at http://bugs.percona.com/
key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=45
max_threads=20002
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 = 43781150 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x5ec2a000
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 = 7f1585086e70 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x2c)[0x7ce92c]
/usr/sbin/mysqld(handle_fatal_signal+0x4a1)[0x69ac21]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10340)[0x7f1a66e71340]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x39)[0x7f1a65846cc9]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f1a6584a0d8]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(_ZN9__gnu_cxx27__verbose_terminate_handlerEv+0x155)[0x7f1a65f3b535]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x5e6d6)[0x7f1a65f396d6]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x5e703)[0x7f1a65f39703]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x5f1bf)[0x7f1a65f3a1bf]
/usr/sbin/mysqld(_ZN9Log_event12write_headerEP11st_io_cachem+0x81)[0x73c1c1]
/usr/sbin/mysqld(_ZN28Format_description_log_event5writeEP11st_io_cache+0xeb)[0x73caab]
/usr/sbin/mysqld(_ZN13MYSQL_BIN_LOG4openEPKc13enum_log_typeS1_10cache_typebmbb+0x354)[0x72c5e4]
/usr/sbin/mysqld(_ZN13MYSQL_BIN_LOG13new_file_implEb+0x503)[0x72f4d3]
/usr/sbin/mysqld(_Z16rotate_relay_logP11Master_info+0x2c)[0x53dd6c]
/usr/sbin/mysqld(_Z20reload_acl_and_cacheP3THDmP10TABLE_LISTPi+0x848)[0x65a798]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1772)[0x5a6a02]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x13a)[0x6451fa]
/usr/sbin/mysqld(handle_one_connection+0x4a)[0x6452ea]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8182)[0x7f1a66e69182]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f1a6590a47d]
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): 4099705
Status: NOT_KILLED
Please, take a look at the patch provided and consider implementing it.
There is nothing special in my.cnf (other than some binary and relay logs filtering).
It seems same problem still happens on the intermediate master with 5.5.48-37.8 when FLUSH LOGS is executed there on regular basis to get a chance to save/sync binary logs:
pure virtual method called bugs.percona. com/
terminate called without an active exception
22:40:01 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.
Please help us make Percona Server better by reporting any
bugs at http://
key_buffer_ size=8388608 size=131072 connections= 45 size)*max_ threads = 43781150 K bytes of memory
read_buffer_
max_used_
max_threads=20002
thread_count=38
connection_count=38
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x5ec2a000 mysqld( my_print_ stacktrace+ 0x2c)[0x7ce92c] mysqld( handle_ fatal_signal+ 0x4a1)[ 0x69ac21] 64-linux- gnu/libpthread. so.0(+0x10340) [0x7f1a66e71340 ] 64-linux- gnu/libc. so.6(gsignal+ 0x39)[0x7f1a658 46cc9] 64-linux- gnu/libc. so.6(abort+ 0x148)[ 0x7f1a6584a0d8] x86_64- linux-gnu/ libstdc+ +.so.6( _ZN9__gnu_ cxx27__ verbose_ terminate_ handlerEv+ 0x155)[ 0x7f1a65f3b535] x86_64- linux-gnu/ libstdc+ +.so.6( +0x5e6d6) [0x7f1a65f396d6 ] x86_64- linux-gnu/ libstdc+ +.so.6( +0x5e703) [0x7f1a65f39703 ] x86_64- linux-gnu/ libstdc+ +.so.6( +0x5f1bf) [0x7f1a65f3a1bf ] mysqld( _ZN9Log_ event12write_ headerEP11st_ io_cachem+ 0x81)[0x73c1c1] mysqld( _ZN28Format_ description_ log_event5write EP11st_ io_cache+ 0xeb)[0x73caab] mysqld( _ZN13MYSQL_ BIN_LOG4openEPK c13enum_ log_typeS1_ 10cache_ typebmbb+ 0x354)[ 0x72c5e4] mysqld( _ZN13MYSQL_ BIN_LOG13new_ file_implEb+ 0x503)[ 0x72f4d3] mysqld( _Z16rotate_ relay_logP11Mas ter_info+ 0x2c)[0x53dd6c] mysqld( _Z20reload_ acl_and_ cacheP3THDmP10T ABLE_LISTPi+ 0x848)[ 0x65a798] mysqld( _Z16dispatch_ command19enum_ server_ commandP3THDPcj +0x1772) [0x5a6a02] mysqld( _Z24do_ handle_ one_connectionP 3THD+0x13a) [0x6451fa] mysqld( handle_ one_connection+ 0x4a)[0x6452ea] 64-linux- gnu/libpthread. so.0(+0x8182) [0x7f1a66e69182 ] 64-linux- gnu/libc. so.6(clone+ 0x6d)[0x7f1a659 0a47d]
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 = 7f1585086e70 thread_stack 0x40000
/usr/sbin/
/usr/sbin/
/lib/x86_
/lib/x86_
/lib/x86_
/usr/lib/
/usr/lib/
/usr/lib/
/usr/lib/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/lib/x86_
/lib/x86_
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): 4099705
Status: NOT_KILLED
Please, take a look at the patch provided and consider implementing it.
There is nothing special in my.cnf (other than some binary and relay logs filtering).