Details
-
Bug
-
Status: Done
-
High
-
Resolution: Done
-
None
-
None
-
None
Description
**Reported in Launchpad by Jai Gupta last update 23-06-2015 05:34:36
Percona-XtraDB-Cluster-galera-3-3.7-1.3254.rhel6.x86_64
Percona-XtraDB-Cluster-server-56-5.6.20-25.7.888.el6.x86_64
Percona-XtraDB-Cluster-galera-3-debuginfo-3.7-1.3254.rhel6.x86_64
Percona-XtraDB-Cluster-client-56-5.6.20-25.7.888.el6.x86_64
Percona-XtraDB-Cluster-56-debuginfo-5.6.20-25.7.888.el6.x86_64
percona-nagios-plugins-1.1.4-1.noarch
Percona-XtraDB-Cluster-shared-56-5.6.20-25.7.888.el6.x86_64
percona-release-0.0-1.x86_64
percona-xtrabackup-2.2.3-4982.el6.x86_64
Percona-XtraDB-Cluster-test-56-5.6.20-25.7.888.el6.x86_64
Percona-XtraDB-Cluster-garbd-3-3.7-1.3254.rhel6.x86_64
Percona-XtraDB-Cluster-full-56-5.6.20-25.7.888.el6.x86_64
2014-09-22 00:15:47 7f285a4f3700 InnoDB: Assertion failure in thread 139811290560256 in file row0mysql.cc line 3383
InnoDB: Failing assertion: !DICT_TF2_FLAG_IS_SET(table, DICT_TF2_TEMPORARY)
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
05:15:47 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 XtraDB Cluster better by reporting any
bugs at https://bugs.launchpad.net/percona-xtradb-cluster
key_buffer_size=25165824
read_buffer_size=131072
max_used_connections=182
max_threads=202
thread_count=52
connection_count=3
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 105202 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x137f96010
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 = 7f285a4f2d38 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x8f5835]
/usr/sbin/mysqld(handle_fatal_signal+0x4b4)[0x664384]
/lib64/libpthread.so.0(+0xf710)[0x7f5fad3a8710]
/lib64/libc.so.6(gsignal+0x35)[0x7f5fab7f1635]
/lib64/libc.so.6(abort+0x175)[0x7f5fab7f2e15]
/usr/sbin/mysqld[0x9ac7bb]
/usr/sbin/mysqld[0x91fdfe]
/usr/sbin/mysqld(_ZN22Sql_cmd_truncate_table16handler_truncateEP3THDP10TABLE_LISTb+0xe0)[0x877cc0]
/usr/sbin/mysqld(_ZN22Sql_cmd_truncate_table14truncate_tableEP3THDP10TABLE_LIST+0x363)[0x8784e3]
/usr/sbin/mysqld(_ZN22Sql_cmd_truncate_table7executeEP3THD+0x5e)[0x87858e]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x138e)[0x6e990e]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x658)[0x6eedc8]
/usr/sbin/mysqld[0x6eef21]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1362)[0x6f0a92]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x20a)[0x6f261a]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x17f)[0x6bb06f]
/usr/sbin/mysqld(handle_one_connection+0x47)[0x6bb247]
/usr/sbin/mysqld(pfs_spawn_thread+0x12a)[0xaee54a]
/lib64/libpthread.so.0(+0x79d1)[0x7f5fad3a09d1]
/lib64/libc.so.6(clone+0x6d)[0x7f5fab8a786d]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f260c1fea90): is an invalid pointer
Connection ID (thread ID): 5046789
Status: NOT_KILLED
You may download the Percona XtraDB Cluster operations manual by visiting
http://www.percona.com/software/percona-xtradb-cluster/. You may find information
in the manual which will help you identify the cause of the crash.
140922 00:15:48 mysqld_safe Number of processes running now: 0
140922 00:15:48 mysqld_safe WSREP: not restarting wsrep node automatically
140922 00:15:48 mysqld_safe mysqld from pid file /var/lib/mysql/xxxx.pid ended