Bug #71933 MySQL server has gone away
Submitted: 5 Mar 2014 10:19 Modified: 5 Mar 2014 10:56
Reporter: Veeresh Bhat Email Updates:
Status: Can't repeat Impact on me:
Category:MySQL Server Severity:S3 (Non-critical)
Version:5-5-8 OS:Other (SLES 10)
Assigned to: CPU Architecture:Any
Tags: MySQL server has gone away

[5 Mar 2014 10:19] Veeresh Bhat
We can notice a lot of following errors:

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.

It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2315827 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0xa6cd6f0
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 = 0x47912158 thread_stack 0x40000
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0xa7b0d58 = SELECT DISTINCT column_name FROM information_schema.columns WHERE table_name='agm_commissionclaiminginvoice_master' AND table_schema=SCHEMA() AND column_name NOT IN ('bigram_sig_p0', 'bigram_sig_p1', 'bigram_sig_p2', 'bigram_sig_p3', 'bigram_sig_p4', 'bigram_sig_p5', 'bigram_sig_p6', 'bigram_sig_p7', 'sgram_sig_p0', 'sgram_sig_p1', 'sgram_sig_p2', 'sgram_sig_p3', 'sgram_sig_p4', 'sgram_sig_p5', 'sgram_sig_p6', 'sgram_sig_p7') ORDER BY ordinal_position
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.
140305 10:44:16 mysqld_safe Number of processes running now: 0
140305 10:44:16 mysqld_safe mysqld restarted
140305 10:44:16 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use InnoDB's own implementation
InnoDB: Compressed tables use zlib 1.2.3
140305 10:44:16  InnoDB: Using Linux native AIO
140305 10:44:16  InnoDB: Initializing buffer pool, size = 1.5G
140305 10:44:16  InnoDB: Completed initialization of buffer pool
140305 10:44:16  InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 148711596186
140305 10:44:16  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...
InnoDB: Doing recovery: scanned up to log sequence number 148711598300
140305 10:44:18  InnoDB: 1.1.4 started; log sequence number 148711598300
140305 10:44:18 [Note] Event Scheduler: Loaded 0 events
140305 10:44:18 [Note] /softs/mysql/5-5-8/bin/mysqld: ready for connections.
Version: '5.5.8'  socket: '/oradata5/mysql/GHI09/mysql.sock'  port: 3414  Source distribution

How to repeat:
Since, It is a DEV system, not sure, which operation would have caused this issue.

Suggested fix:
Not available
[5 Mar 2014 10:31] MySQL Verification Team
5.5.8 is far too old, the current version is 5.5.36:

This looks like a known and fixed bug:
[5 Mar 2014 10:56] Veeresh Bhat
Hi Shane,

Thanks for the reply, Is there any fix available for 5.5.8 ?