Percona Server 5.7 crashed with signal 11

Bug #1574417 reported by Vyacheslav
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
New
Undecided
Unassigned

Bug Description

Hello.

Got problem with crashes mysql server.

mysql Ver 14.14 Distrib 5.7.11-4, for Linux (x86_64) using 6.0
CentOS release 6.7 (Final)

Info about error:

23:46:36 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
Please help us make Percona Server better by reporting any
bugs at http://bugs.percona.com/

key_buffer_size=536870912
read_buffer_size=2097152
max_used_connections=108
max_threads=1501
thread_count=17
connection_count=17
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 6689337 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f8428208e90
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 = 7f84bc376d40 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x2c)[0xec0a9c]
/usr/sbin/mysqld(handle_fatal_signal+0x461)[0x79b8c1]
/lib64/libpthread.so.0[0x3996a0f7e0]
/usr/sbin/mysqld(_Z29create_table_share_index_statPK11TABLE_SHAREj+0xa8)[0x1251a28]
/usr/sbin/mysqld(_ZN15PFS_table_share25find_or_create_index_statEPK11TABLE_SHAREj+0x47)[0x1252067]
/usr/sbin/mysqld(_Z26find_or_create_table_shareP10PFS_threadbPK11TABLE_SHARE+0x47f)[0x12541af]
/usr/sbin/mysqld(_Z15get_table_shareP3THDP10TABLE_LISTPKcmjPij+0x1da)[0xc471ea]
/usr/sbin/mysqld(_Z10open_tableP3THDP10TABLE_LISTP18Open_table_context+0xb33)[0xc48313]
/usr/sbin/mysqld(_Z11open_tablesP3THDPP10TABLE_LISTPjjP19Prelocking_strategy+0x5f2)[0xc4f922]
/usr/sbin/mysqld(_Z20open_and_lock_tablesP3THDP10TABLE_LISTjP19Prelocking_strategy+0x35)[0xc50125]
/usr/sbin/mysqld[0xdf989a]
/usr/sbin/mysqld(_ZN19Sql_cmd_check_table7executeEP3THD+0xc1)[0xdfb431]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THDb+0x1365)[0xca22a5]
/usr/sbin/mysqld(_Z11mysql_parseP3THDP12Parser_state+0x5b5)[0xca85d5]
/usr/sbin/mysqld(_Z16dispatch_commandP3THDPK8COM_DATA19enum_server_command+0x92f)[0xca8f7f]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x1b7)[0xcaa917]
/usr/sbin/mysqld(handle_connection+0x2a8)[0xd6b0a8]
/usr/sbin/mysqld(pfs_spawn_thread+0x1b4)[0x12308d4]
/lib64/libpthread.so.0[0x3996a07aa1]
/lib64/libc.so.6(clone+0x6d)[0x39966e893d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f8428222850): is an invalid pointer
Connection ID (thread ID): 717
Status: NOT_KILLED

You may download the Percona Server operations manual by visiting
http://www.percona.com/software/percona-server/. You may find information
in the manual which will help you identify the cause of the crash.

summary: - mysqld got signal 11
+ Percona Server 5.7 crashed with signal 11
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3417

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.