MySQL Bugs: #43806: mysql got crashed and hung with signal 6 ,signal 8 and signal 11.

Bug #43806	mysql got crashed and hung with signal 6 ,signal 8 and signal 11.
Submitted:	23 Mar 2009 15:15	Modified:	24 Apr 2009 7:38
Reporter:	kris dba	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	5.0.51a-log	OS:	Linux
Assigned to:		CPU Architecture:	Any
Tags:	crashed, mysql hung, replication slave

Description:
Hi,
we are using mysql5.0.51 on x86_64 linux GNU/Linux with 2.6.18-53.el5 kernel.
The server is acting as a replication slave.
slave sql process got failed  due to a failed transaction from master and other sessions got hung.
we had to restart mysql and when try to start replication slave process mysql got crashed for # of times resuting into a hung state.
the error log file entry is as follows.
The disk and filesystem status looks good.

How to repeat:
NA

Thank you for the report.

Error log contains:

----<Q>----
090323  7:06:16  InnoDB: Error: table 'tmp/#sqlb1e_39e6_2'
InnoDB: in InnoDB data dictionary has tablespace id 14290094,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
----</Q>----

Have you tried this suggestion?

Thank you for the feedback.

Could you please check if slave affected by the same problem as master? Also version 5.0.51 is old and many bugs were fixed since. Please upgrade to current version 5.0.77 and examine if it solves the problem.

Thank you for the feedback.

There are several different errors in the log file.

What to do with errors occured because of temporary tables I described in comment "[23 Mar 16:52] Sveta Smirnova"

If process latest one "*** glibc detected *** /usr/local/mysql/libexec/mysqld: free(): invalid pointer:" please:

1. Upgrade to current version 5.0.77: there are many replication bugs were fixed since version 5.0.51 which you use and inform us if problem still exists.

2. If problem exists in latest version upload your 'mysql-bin.000110' and 'mysql-relay-bin.000277' files to our FTP server as described in "Files" section.

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