I can confirm the problem on the same version:
mysql> select @@version,@@version_comment;
+----------------+---------------------------------------------------------------------------------------------------+
| @@version | @@version_comment |
+----------------+---------------------------------------------------------------------------------------------------+
| 5.6.19-67.0-56 | Percona XtraDB Cluster (GPL), Release rel67.0, Revision 824, WSREP version 25.6, wsrep_25.6.r4111 |
+----------------+---------------------------------------------------------------------------------------------------+
1 row in set (0.00 sec)
However, the crash does not happen when wsrep_provider is not set:
mysql> show status like 'ws%';
+--------------------------+----------------------+
| Variable_name | Value |
+--------------------------+----------------------+
| wsrep_cluster_conf_id | 18446744073709551615 |
| wsrep_cluster_size | 0 |
| wsrep_cluster_state_uuid | |
| wsrep_cluster_status | Disconnected |
| wsrep_connected | OFF |
| wsrep_local_bf_aborts | 0 |
| wsrep_local_index | 18446744073709551615 |
| wsrep_provider_name | |
| wsrep_provider_vendor | |
| wsrep_provider_version | |
| wsrep_ready | ON |
+--------------------------+----------------------+
11 rows in set (0.00 sec)
When wsrep_provider is enabled, I get the same crash:
mysql> INSERT INTO r8kmb_redirect_links VALUES (550,'http://mysite.com/images/download/ßуñûічýøù_ôþóþòір_þфõÑ.doc','','','',0,'2013-07-15 14:29:42','0000-00-00 00:00:00');
ERROR 2013 (HY000): Lost connection to MySQL server during query
2014-07-24 23:55:33 7f73886e9700 InnoDB: Assertion failure in thread 140134186915584 in file ha_innodb.cc line 6759
InnoDB: Failing assertion: buff <= buff_start + buff_len
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.
21:55:33 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=8388608
read_buffer_size=131072
max_used_connections=1
max_threads=153
thread_count=3
connection_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 69256 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x2d2dcf0
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 = 7f73886e8d38 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x8f36b5]
/usr/sbin/mysqld(handle_fatal_signal+0x4c4)[0x6635c4]
/usr/lib64/libpthread.so.0[0x336620f750]
/usr/lib64/libc.so.6(gsignal+0x39)[0x3365a35c39]
/usr/lib64/libc.so.6(abort+0x148)[0x3365a37348]
/usr/sbin/mysqld[0x909d4e]
/usr/sbin/mysqld(_ZN11ha_innobase17wsrep_append_keysEP3THDbPKhS3_+0x1d4)[0x90a654]
/usr/sbin/mysqld[0x9152b9]
/usr/sbin/mysqld(_ZN7handler12ha_write_rowEPh+0xa9)[0x5a7c99]
/usr/sbin/mysqld(_Z12write_recordP3THDP5TABLEP9COPY_INFOS4_+0x8a)[0x6cbdca]
/usr/sbin/mysqld(_Z12mysql_insertP3THDP10TABLE_LISTR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb+0xb70)[0x6d3940]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0xf70)[0x6e8050]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x658)[0x6ed768]
/usr/sbin/mysqld[0x6ed8c1]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1362)[0x6ef412]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x1e3)[0x6f0f73]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x17f)[0x6b9bdf]
/usr/sbin/mysqld(handle_one_connection+0x47)[0x6b9db7]
/usr/sbin/mysqld(pfs_spawn_thread+0x12a)[0xae9b4a]
/usr/lib64/libpthread.so.0[0x3366207f33]
/usr/lib64/libc.so.6(clone+0x6d)[0x3365af4ded]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f7354004f50): is an invalid pointer
Connection ID (thread ID): 3
Status: NOT_KILLED
I can confirm the problem on the same version: @@version_ comment; ------- ---+--- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- -----+ ------- ---+--- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- -----+ ------- ---+--- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- -----+
mysql> select @@version,
+------
| @@version | @@version_comment |
+------
| 5.6.19-67.0-56 | Percona XtraDB Cluster (GPL), Release rel67.0, Revision 824, WSREP version 25.6, wsrep_25.6.r4111 |
+------
1 row in set (0.00 sec)
However, the crash does not happen when wsrep_provider is not set: ------- ------- ------+ ------- ------- ------- -+ ------- ------- ------+ ------- ------- ------- -+ conf_id | 184467440737095 51615 | state_uuid | | status | Disconnected | bf_aborts | 0 | 51615 | vendor | | version | | ------- ------- ------+ ------- ------- ------- -+
mysql> show status like 'ws%';
+------
| Variable_name | Value |
+------
| wsrep_cluster_
| wsrep_cluster_size | 0 |
| wsrep_cluster_
| wsrep_cluster_
| wsrep_connected | OFF |
| wsrep_local_
| wsrep_local_index | 184467440737095
| wsrep_provider_name | |
| wsrep_provider_
| wsrep_provider_
| wsrep_ready | ON |
+------
11 rows in set (0.00 sec)
mysql> INSERT INTO r8kmb_redirect_ links VALUES (550,'http:// mysite. com/images/ download/ß ÑÆ ’à±Ã »Ã‘  œÃƒâ€˜Ã¢ €¡Ã ½Ã ¸Ã ¹_à´Ã ¾Ã ³Ã ¾Ã ²Ã‘  œÃƒâ€˜Ã¢ ‚¬_à¾Ã‘ „àµÃ‘ .doc',' ','','' ,0,'2013- 07-15 14:29:42' ,'0000- 00-00 00:00:00');
Query OK, 1 row affected (0.09 sec)
When wsrep_provider is enabled, I get the same crash:
mysql> INSERT INTO r8kmb_redirect_ links VALUES (550,'http:// mysite. com/images/ download/ß ÑÆ ’à±Ã »Ã‘  œÃƒâ€˜Ã¢ €¡Ã ½Ã ¸Ã ¹_à´Ã ¾Ã ³Ã ¾Ã ²Ã‘  œÃƒâ€˜Ã¢ ‚¬_à¾Ã‘ „àµÃ‘ .doc',' ','','' ,0,'2013- 07-15 14:29:42' ,'0000- 00-00 00:00:00');
ERROR 2013 (HY000): Lost connection to MySQL server during query
2014-07-24 23:55:33 7f73886e9700 InnoDB: Assertion failure in thread 140134186915584 in file ha_innodb.cc line 6759 bugs.mysql. com. dev.mysql. com/doc/ refman/ 5.6/en/ forcing- innodb- recovery. html /bugs.launchpad .net/percona- xtradb- cluster
InnoDB: Failing assertion: buff <= buff_start + buff_len
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://
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://
InnoDB: about forcing recovery.
21:55:33 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:/
key_buffer_ size=8388608 size=131072 connections= 1 size)*max_ threads = 69256 K bytes of memory
read_buffer_
max_used_
max_threads=153
thread_count=3
connection_count=1
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: 0x2d2dcf0 mysqld( my_print_ stacktrace+ 0x35)[0x8f36b5] mysqld( handle_ fatal_signal+ 0x4c4)[ 0x6635c4] libpthread. so.0[0x336620f7 50] libc.so. 6(gsignal+ 0x39)[0x3365a35 c39] libc.so. 6(abort+ 0x148)[ 0x3365a37348] mysqld[ 0x909d4e] mysqld( _ZN11ha_ innobase17wsrep _append_ keysEP3THDbPKhS 3_+0x1d4) [0x90a654] mysqld[ 0x9152b9] mysqld( _ZN7handler12ha _write_ rowEPh+ 0xa9)[0x5a7c99] mysqld( _Z12write_ recordP3THDP5TA BLEP9COPY_ INFOS4_ +0x8a)[ 0x6cbdca] mysqld( _Z12mysql_ insertP3THDP10T ABLE_LISTR4List I4ItemERS3_ IS5_ES6_ S6_15enum_ duplicatesb+ 0xb70)[ 0x6d3940] mysqld( _Z21mysql_ execute_ commandP3THD+ 0xf70)[ 0x6e8050] mysqld( _Z11mysql_ parseP3THDPcjP1 2Parser_ state+0x658) [0x6ed768] mysqld[ 0x6ed8c1] mysqld( _Z16dispatch_ command19enum_ server_ commandP3THDPcj +0x1362) [0x6ef412] mysqld( _Z10do_ commandP3THD+ 0x1e3)[ 0x6f0f73] mysqld( _Z24do_ handle_ one_connectionP 3THD+0x17f) [0x6b9bdf] mysqld( handle_ one_connection+ 0x47)[0x6b9db7] mysqld( pfs_spawn_ thread+ 0x12a)[ 0xae9b4a] libpthread. so.0[0x3366207f 33] libc.so. 6(clone+ 0x6d)[0x3365af4 ded]
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 = 7f73886e8d38 thread_stack 0x40000
/usr/sbin/
/usr/sbin/
/usr/lib64/
/usr/lib64/
/usr/lib64/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/lib64/
/usr/lib64/
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f7354004f50): is an invalid pointer
Connection ID (thread ID): 3
Status: NOT_KILLED