| 2017-05-23 12:24:42 |
Andriy Velihotskyi |
description |
I have 5.6.34-79.1-log Percona Server.
During the following operation mysql got signal 11 and has been restarted:
~~~~~~~~~~~~~~~~~~~~~~~~
mysql> CHECK TABLE task_2014 QUICK;
ERROR 2013 (HY000): Lost connection to MySQL server during query
~~~~~~~~~~~~~~~~~~~~~~~~
Also the same problem (mysql restart) occurs when I am trying to dump the table using mydumper.
The output from the log file:
~~~~~~~~~~~~~~~~~~~~~~~~
11:56:14 UTC - 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.
Please help us make Percona Server better by reporting any
bugs at http://bugs.percona.com/
key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=13
max_threads=258
thread_count=13
connection_count=11
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 119025 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x2b7d800
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 = 7fe084088d40 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x2c)[0x8d750c]
/usr/sbin/mysqld(handle_fatal_signal+0x461)[0x65a2b1]
/lib64/libpthread.so.0[0x3f5720f4a0]
/usr/sbin/mysqld(_ZN10ha_archive10unpack_rowEP11azio_streamPh+0x122)[0x8e88a2]
/usr/sbin/mysqld(_ZN10ha_archive5checkEP3THDP15st_ha_check_opt+0x121)[0x8e95c1]
/usr/sbin/mysqld(_ZN7handler8ha_checkEP3THDP15st_ha_check_opt+0x7a)[0x59fb9a]
/usr/sbin/mysqld[0x812bc3]
/usr/sbin/mysqld(_ZN19Sql_cmd_check_table7executeEP3THD+0xb4)[0x8136e4]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x1f9e)[0x6dd40e]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x5b8)[0x6e2728]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1051)[0x6e3f11]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x1a2)[0x6b06a2]
/usr/sbin/mysqld(handle_one_connection+0x40)[0x6b0740]
/usr/sbin/mysqld(pfs_spawn_thread+0x146)[0x91b576]
/lib64/libpthread.so.0[0x3f572077f1]
/lib64/libc.so.6(clone+0x6d)[0x3f56ae5ccd]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fd77c004bf0): is an invalid pointer
Connection ID (thread ID): 1508
Status: NOT_KILLED
~~~~~~~~~~~~~~~~~~~~~~~~
P.S. I have found the similar case here: https://bugs.launchpad.net/percona-server/+bug/1340416
However it seems |
I have 5.6.34-79.1-log Percona Server.
During the following operation mysql got signal 11 and has been restarted:
~~~~~~~~~~~~~~~~~~~~~~~~
mysql> CHECK TABLE task_2014 QUICK;
ERROR 2013 (HY000): Lost connection to MySQL server during query
~~~~~~~~~~~~~~~~~~~~~~~~
Also the same problem (mysql restart) occurs when I am trying to dump the table using mydumper.
The output from the log file:
~~~~~~~~~~~~~~~~~~~~~~~~
11:56:14 UTC - 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.
Please help us make Percona Server better by reporting any
bugs at http://bugs.percona.com/
key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=13
max_threads=258
thread_count=13
connection_count=11
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 119025 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x2b7d800
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 = 7fe084088d40 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x2c)[0x8d750c]
/usr/sbin/mysqld(handle_fatal_signal+0x461)[0x65a2b1]
/lib64/libpthread.so.0[0x3f5720f4a0]
/usr/sbin/mysqld(_ZN10ha_archive10unpack_rowEP11azio_streamPh+0x122)[0x8e88a2]
/usr/sbin/mysqld(_ZN10ha_archive5checkEP3THDP15st_ha_check_opt+0x121)[0x8e95c1]
/usr/sbin/mysqld(_ZN7handler8ha_checkEP3THDP15st_ha_check_opt+0x7a)[0x59fb9a]
/usr/sbin/mysqld[0x812bc3]
/usr/sbin/mysqld(_ZN19Sql_cmd_check_table7executeEP3THD+0xb4)[0x8136e4]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x1f9e)[0x6dd40e]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x5b8)[0x6e2728]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1051)[0x6e3f11]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x1a2)[0x6b06a2]
/usr/sbin/mysqld(handle_one_connection+0x40)[0x6b0740]
/usr/sbin/mysqld(pfs_spawn_thread+0x146)[0x91b576]
/lib64/libpthread.so.0[0x3f572077f1]
/lib64/libc.so.6(clone+0x6d)[0x3f56ae5ccd]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fd77c004bf0): is an invalid pointer
Connection ID (thread ID): 1508
Status: NOT_KILLED
~~~~~~~~~~~~~~~~~~~~~~~~
P.S. I have found the similar case here: https://bugs.launchpad.net/percona-server/+bug/1340416 |
|
