mysqld got signal 11
Description
Environment
Attachments
Smart Checklist
Activity
Carsten Blume June 4, 2018 at 2:23 PM
any news on this?
btw: after we activated PDO::ATTR_EMULATE_PREPARES in php, problems seems to be solved.
Carsten Blume May 17, 2018 at 3:12 PM
i've attached backtrace from gdb and coredump
Carsten Blume May 17, 2018 at 3:12 PM
OS:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 8.10 (jessie)
Release: 8.10
Codename: jessieKernel:
$ uname -a
Linux fmpt-sql-v1.eu-w1.odmedia.net 3.16.0-6-amd64 #1 SMP Debian 3.16.56-1 (2018-04-28) x86_64 GNU/Linuxinstalled packages:
ii percona-toolkit 3.0.9-1.jessie amd64 Advanced MySQL and system command-line tools
ii percona-xtrabackup 2.3.10-1.jessie amd64 Open source backup tool for InnoDB and XtraDB
ii percona-xtradb-cluster-5.6-dbg 5.6.39-26.25-1.jessie amd64 Debugging package for Percona XtraDB Cluster
ii percona-xtradb-cluster-56 5.6.39-26.25-1.jessie amd64 Percona XtraDB Cluster with Galera
ii percona-xtradb-cluster-client-5.6 5.6.39-26.25-1.jessie amd64 Percona XtraDB Cluster database client binaries
ii percona-xtradb-cluster-common-5.6 5.6.39-26.25-1.jessie amd64 Percona XtraDB Cluster database common files (e.g. /etc/mysql/my.cnf)
ii percona-xtradb-cluster-galera-3 3.25-1.jessie amd64 Metapackage for latest version of galera3.
ii percona-xtradb-cluster-galera-3.x 3.25-1.jessie amd64 Galera components of Percona XtraDB Cluster
ii percona-xtradb-cluster-server-5.6 5.6.39-26.25-1.jessie amd64 Percona XtraDB Cluster database server binaries
Details
Details
Assignee
Reporter
Carsten BlumeAffects versions
Priority
MediumSmart Checklist
Open Smart Checklist
Smart Checklist
10:43:21 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 XtraDB Cluster better by reporting any
bugs at https://jira.percona.com/projects/PXC/issues
key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=66
max_threads=1002
thread_count=67
connection_count=65
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 415674 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x339cbb0
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 = 7fea170b7e48 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x2c)[0x91826c]
/usr/sbin/mysqld(handle_fatal_signal+0x479)[0x692429]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7febd6b1b890]
/lib/x86_64-linux-gnu/libc.so.6(+0x92040)[0x7febd4afd040]
/usr/sbin/mysqld[0x959741]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x3b6)[0x71c536]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x229)[0x71ec19]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x172)[0x6e6ed2]
/usr/sbin/mysqld(handle_one_connection+0x40)[0x6e70d0]
/usr/sbin/mysqld(pfs_spawn_thread+0x146)[0x955db6]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7febd6b14064]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7febd4b5362d]