Bug #69239 Mysql is gone away
Submitted: 15 May 2013 8:43 Modified: 15 May 2013 8:57
Reporter: Luk Has Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server Severity:S1 (Critical)
Version: OS:Any
Assigned to: CPU Architecture:Any
Tags: 2006, can not save, Mysql is gone away

[15 May 2013 8:43] Luk Has
Description:
130515 10:30:04 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.5.16'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Community Server (GPL) by Remi
 len 232; hex a810119c077f0000b1c052b5077f000080b8c0b1077f00000500000000000000020000000000000005000080000000000300000000000000020000000000000000000000000000000300000000000000010000000000000002000000000000000801009c077f000088d4359c077f00008100000000000000ffffffffffffffffe800009c077f000001000000000000008344510700000000ad6b399c077f00000200000000000000010000000000000080b8c0b1077f0000000000000000000060e111770000000002000000000000000000000000000000a86b399c077f00001000000000000000; asc           R                                                                                               5                                      DQ      k9                                     `  w                     k9             ;
130515 10:30:38  InnoDB: Assertion failure in thread 139670916429568 in file btr0pcur.c line 236
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
130515 10:30:38 - 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.

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

Thread pointer: 0x2c81170
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 = 0x7f07ab5bed98 thread_stack 0x40000
/usr/libexec/mysqld(my_print_stacktrace+0x33)[0x77bd03]
/usr/libexec/mysqld(handle_segfault+0x465)[0x50fde5]
/lib64/libpthread.so.0[0x3fb200f500]
/lib64/libc.so.6(gsignal+0x35)[0x3fb18328a5]
/lib64/libc.so.6(abort+0x175)[0x3fb1834085]
/usr/libexec/mysqld[0x83f734]
/usr/libexec/mysqld[0x7f8cb9]
/usr/libexec/mysqld[0x7f91c6]
/usr/libexec/mysqld[0x7dcb2c]
/usr/libexec/mysqld(_ZN26QUICK_GROUP_MIN_MAX_SELECT11next_prefixEv+0x126)[0x7119c6]
/usr/libexec/mysqld(_ZN26QUICK_GROUP_MIN_MAX_SELECT8get_nextEv+0x3b)[0x713fbb]
/usr/libexec/mysqld[0x723d71]
/usr/libexec/mysqld(_Z10sub_selectP4JOINP13st_join_tableb+0x63)[0x5a2e73]
/usr/libexec/mysqld[0x5a36fe]
/usr/libexec/mysqld(_ZN4JOIN4execEv+0xbde)[0x5b5b4e]
/usr/libexec/mysqld(_Z12mysql_selectP3THDPPP4ItemP10TABLE_LISTjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x162)[0x5b1952]
/usr/libexec/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x174)[0x5b7174]
/usr/libexec/mysqld[0x5797c7]
/usr/libexec/mysqld(_Z21mysql_execute_commandP3THD+0x2f09)[0x57eca9]
/usr/libexec/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x169)[0x5802a9]
/usr/libexec/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x12f1)[0x581d41]
/usr/libexec/mysqld(_Z24do_handle_one_connectionP3THD+0xd2)[0x60ed62]
/usr/libexec/mysqld(handle_one_connection+0x50)[0x60ee70]
/lib64/libpthread.so.0[0x3fb2007851]
/lib64/libc.so.6(clone+0x6d)[0x3fb18e811d]

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

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
130515 10:30:38 mysqld_safe Number of processes running now: 0
130515 10:30:38 mysqld_safe mysqld restarted
130515 10:30:38 [Note] Plugin 'FEDERATED' is disabled.
130515 10:30:38 InnoDB: The InnoDB memory heap is disabled
130515 10:30:38 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130515 10:30:38 InnoDB: Compressed tables use zlib 1.2.3
130515 10:30:38 InnoDB: Using Linux native AIO
130515 10:30:38 InnoDB: Initializing buffer pool, size = 128.0M
130515 10:30:38 InnoDB: Completed initialization of buffer pool
130515 10:30:38 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
130515 10:30:38  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
130515 10:30:39  InnoDB: Waiting for the background threads to start
130515 10:30:40 InnoDB: 1.1.8 started; log sequence number 36754986640
130515 10:30:40 [Note] Event Scheduler: Loaded 0 events
130515 10:30:40 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.5.16'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Community Server (GPL) by Remi

"

can anyone help me?

How to repeat:
Hi from some time i have very strange error

My my.cnf confing is here:

"
[mysqld]
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
port=3306
#bind-address=127.0.0.1
bind-address=localhost
#bind-address=192.168.0.107
#bind-address=82.160.17.218
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0
#skip-networking
# Semisynchronous Replication
# http://dev.mysql.com/doc/refman/5.5/en/replication-semisync.html
# uncomment next line on MASTER
;plugin-load=rpl_semi_sync_master=semisync_master.so
# uncomment next line on SLAVE
;plugin-load=rpl_semi_sync_slave=semisync_slave.so

# Others options for Semisynchronous Replication
;rpl_semi_sync_master_enabled=1
;rpl_semi_sync_master_timeout=10
;rpl_semi_sync_slave_enabled=1

# http://dev.mysql.com/doc/refman/5.5/en/performance-schema.html
;performance_schema
max_allowed_packet=1024M
wait_timeout=28800
interactive_timeout = 28800

tmpdir=/tmp
[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid

"

i made max_allowe_packet and waiting time out , because i readed this solution is google, but seems not working.

In mysqld.log i have these message when error - see description
[15 May 2013 8:57] MySQL Verification Team
Hi!  please upgrade to the most recent 5.5.31.
This is a known and fixed bug, most likely a duplicate of:
http://bugs.mysql.com/bug.php?id=61842