MySQL Bugs: #29879: mysql 4.1.23 crashed on FLUSH MASTER

Bug #29879	mysql 4.1.23 crashed on FLUSH MASTER
Submitted:	18 Jul 2007 19:22	Modified:	6 Sep 2007 9:04
Reporter:	Dathan Pattishall	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	4.1.23	OS:	Linux (2.6.9-34.ELsmp #1 SMP Fri Feb 24 16:56:28 EST 2006 x86_64 x86_64 x86_64 GNU/Linux)
Assigned to:		CPU Architecture:	Any
Tags:	mysqld 4.1.23

Description:
Server doing 7000 qps a COMMAND FLUSH MASTER was issued, server crashed

070718 19:05:24 - 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.

Number of processes running now: 2
mysqld process hanging, pid 17267 - killed
mysqld process hanging, pid 17267 - killed
070718 19:05:24  mysqld restarted
070718 19:05:24 [ERROR] Can't start server: Bind on TCP/IP port: Address already in use
070718 19:05:24 [ERROR] Do you already have another mysqld server running on port: 3306 ?
070718 19:05:24 [ERROR] Aborting

070718 19:05:24 [Note] /usr/sbin/mysqld: Shutdown complete

070718 19:05:24  mysqld ended

070718 19:11:11  mysqld started
070718 19:11:14  InnoDB: Database was not shut down normally!

How to repeat:

Build mysqld on x86_64 execute many qps, have a few slaves connected to it, FLUSH MASTER on the x86_64 box

Suggested fix:
FLUSH master needs to be looked at.

Hmm I wonder if this was due to backlog being set to 500

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

free

Linux command. Can you try to enable core files creation and get a core dump for the crash if it will happen again?

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