MySQL Bugs: #33535: mysqld got signal 11

Bug #33535	mysqld got signal 11
Submitted:	27 Dec 2007 14:29	Modified:	18 Mar 2008 4:45
Reporter:	Collin Jackson	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	5.0.45	OS:	Linux (Fedora Core 7 x86_64)
Assigned to:		CPU Architecture:	Any

Description:
I am trying to migrate a database from another server running fedora core 5 and mysql version 5.0.27 to my server running Fedora core 7 with mysql version 5.0.45.  
When I try mysqldump db-name | mysql -h newserver -D db-name  

This is the error I receive on stdout

ERROR 2013 (HY000) at line 49: Lost connection to MySQL server during query
mysqldump: Got errno 32 on write
---

Crash Dump from mysqld.log on FC7 server:

071227 08:02:49  mysqld restarted
071227  8:02:49  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...
071227  8:02:50  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 746894973.
071227  8:02:50  InnoDB: Starting an apply batch of log records to the database$
InnoDB: Progress in percents: 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 2$
InnoDB: Apply batch completed
InnoDB: Doing recovery: scanned up to log sequence number 0 749499475
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 1369 row operations to undo
InnoDB: Trx id counter is 0 19968
071227  8:02:50  InnoDB: Starting an apply batch of log records to the database$
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19$
InnoDB: Apply batch completed
071227  8:02:51  InnoDB: Started; log sequence number 0 749499475
InnoDB: Starting in background the rollback of uncommitted transactions
071227  8:02:51  InnoDB: Rolling back trx with id 0 19489, 1369 rows to undo

InnoDB: Progress in percents: 1 2071227  8:02:51 - 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.

key_buffer_size=0
read_buffer_size=131072
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 21759$
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=(nil)
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...
frame pointer is NULL, did you compile with
-fomit-frame-pointer? Aborting backtrace!
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.
071227 08:02:51  mysqld ended

How to repeat:
Copy Database from Fc5 X86 to FC7 X86_64

Thank you for a problem report. Please, send your my.cnf and the results of:

free

command from FC7.

----my.cnf---
[mysqld]
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
max_allowed_packet=384M   #Added to Configuration for testing purposes
                          #while trying to diagnose this issue
# Default to using old password format for compatibility with mysql 3.x
# clients (those using the mysqlclient10 compatibility package).
old_passwords=1

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

----Output of free--
             total       used       free     shared    buffers     cached
Mem:       2062572    2020164      42408          0     138356    1235152
-/+ buffers/cache:     646656    1415916
Swap:      2031608         52    2031556

Addition Information:

Current System which Database resides on is a Fedora Core 5 x86 AMD Athlon i686 

New System to Migrate Database to is Fedora Core 7 Intel Xeon Dual Core X86_64

Thank you for the feedback.

Could you please upload us part of your dump we can repeat crash with? You can do it privately.

Thank you for the feedback.

File finished with

",(1441858,2,1332397,1443357,'08152775.jpg','',37101,'00cf01c7d9d6$049ee760

****FILE TRUNCATED***"

Is it correct dump or file was broken in time of upload?

It was a partial dump, if I attempted to go past that point the file would have been a few 100MB if you require more of the dump i can try to figure out how to post a larger file. What is the max upload for the bug tracker?

Although maximum limit is 500KB you can upload large file to our FTP server:

If the data you need to attach is more than 500KB, you should create a compressed archive of the data and a README file that describes the data with a filename that includes the bug number (example: bug-data-33535.zip), and use FTP to upload the archive to ftp://ftp.mysql.com/pub/mysql/upload/. Once you have uploaded the file, add a comment to this bug to notify us about it. Note: This directory is unlistable, which means that once you have uploaded your file, you will not be able to see it.

Please, try to repeat with a newer version, 5.0.51a, and inform about the results.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".