MySQL Bugs: #62167: InnoDB: Error: trying to free a corrupt fetch buffer

Bug #62167	InnoDB: Error: trying to free a corrupt fetch buffer
Submitted:	14 Aug 2011 21:05	Modified:	17 Feb 2012 17:30
Reporter:	martin fuxa	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: InnoDB Plugin storage engine	Severity:	S1 (Critical)
Version:	5.5.15	OS:	Linux (CentOS 5.6)
Assigned to:		CPU Architecture:	Any

Description:
After I upgraded from 5.1.58 wich running stable to 5.5.15, I have log of errors and mysql-server restarts.
see attached logs from last day. I can provide older logs if req. Please feel free to ask me for additional information.

How to repeat:
I don't known

of course, upgrade to 5.5 and mysql_upgrade finished without error

grep -vE "OK$" mysql_upgrade55.log
Looking for 'mysql' as: mysql
Looking for 'mysqlcheck' as: mysqlcheck
Running 'mysqlcheck' with connection arguments: '--port=3306' '--socket=/var/lib/mysql/mysql.sock'
Running 'mysqlcheck' with connection arguments: '--port=3306' '--socket=/var/lib/mysql/mysql.sock'
Running 'mysql_fix_privilege_tables'...

I'm trying dump/import all innodb databases. Few db's have problem

1.
> mysqldump some-db -B -r dump.sql && ls -lh dump.sql && ( echo "SET SQL_LOG_BIN=0;" ; cat dump.sql; ) | mysql -B
-rw------- 1 fuxa users 621K Aug 15 20:02 dump.sql
ERROR 2013 (HY000) at line 213: Lost connection to MySQL server during query

2.
on another (second) box with 5.5.15 (i386) import of dump.sql completed without error!
( echo "SET SQL_LOG_BIN=0;" ; cat dump.sql; ) | mysql -B

3.
on second box dump and import back on first problem box - completed without error!

First (problem) box is x86_64.

Test steps 2. and 3. on x86_64 5.5.13
2. ok
3. same problem
ERROR 2013 (HY000) at line 213: Lost connection to MySQL server during query

and drop on 3rd box (5.5.13 x86_64) results
mysql> drop database some-db;
ERROR 2013 (HY000): Lost connection to MySQL server during query

in err log
InnoDB: Error: trying to free a corrupt fetch buffer.
InnoDB: Apparent memory corruption: mem dump
...

for the second time
mysql> drop database some-db;
Query OK, 25 rows affected (0.51 sec)

Thank you for the report.

Back traces look similar to bug #58460 Which 5.5 package have you installed? Is it possible what you mix release version of InnoDB Plugin with debug version of server?

bug #58460 - running "How to repeat" query without problem.

package - all are Mysql RPM's for RHEL 5
> rpm -qi MySQL-server-5.5.15-1.rhel5 |grep Source
Group       : Applications/Databases        Source RPM: MySQL-5.5.15-1.rhel5.src.rpm

SELECT * FROM information_schema.plugins; SELECT @@innodb_version;

Attachment: 2311.log (application/octet-stream, text), 2.62 KiB.

All innodb database were reloaded by way
- mysqldump (lot of errors)
- drop database (lot of errors)
- mysqld stop
- rm ibdata* + ib_logfile*
- mysqld start
- mysql < dump.sql

and problems still continues! Last error log attached.

Thank you for the feedback.

Please try with current version 5.5.20 and if problem still exists lets start testing from first query in the error log:

locate query at line 78 and provide us SHOW CREATE TABLE and SHOW TABLE STATUS LIKE 'table_name' for all tables used in the query, so we can test on our side.

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".