MySQL Bugs: #9605: Signal 11 (segv) -> server crash -> tables corrupt

Bug #9605	Signal 11 (segv) -> server crash -> tables corrupt
Submitted:	4 Apr 2005 11:25	Modified:	27 Jun 2005 15:35
Reporter:	Olaf van der Spek (Basic Quality Contributor)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	4.1.11	OS:	FreeBSD (FreeBSD)
Assigned to:		CPU Architecture:	Any

Description:
My MySQL server is crashing. The error log doesn't include a backtrace. It happens a few times a day, but I've no idea why. What more info is needed to find the cause of this bug?

Error log:
050403 23:02:14  mysqld restarted
050403 23:02:15  InnoDB: Started; log sequence number 0 43922
/usr/local/libexec/mysqld: ready for connections.
Version: '4.1.10-log'  socket: '/tmp/mysql.sock'  port: 3306  FreeBSD port: mysql-server-4.1.10
050404  5:18:46 [ERROR] /usr/local/libexec/mysqld: Incorrect information in file: '.'
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=16384
read_buffer_size=258048
max_used_connections=30
max_connections=200
threads_connected=5
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 63214 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

050404 13:00:09  mysqld restarted
050404 13:00:10  InnoDB: Started; log sequence number 0 43922
/usr/local/libexec/mysqld: ready for connections.
Version: '4.1.10-log'  socket: '/tmp/mysql.sock'  port: 3306  FreeBSD port: mysql-server-4.1.10

How to repeat:
-

this is a binary created from ports collection, right?

there have been several reports lately about these crashing,
using the freebsd binaries from our download site usually solved this so far ...

Yes, probably (FreeBSD port: mysql-server-4.1.11).
I'll submit a bugreport to FreeBSD too and try the binaries from MySQL.

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

Did you the test with our binaries and solved the issue?

Thanks in advance.

As far as I know the server was upgraded to 4.1.12 and the problem disappeared.

Thank you for your bug report. This issue has already been fixed
in the latest released version of that product, which you can download at 
http://www.mysql.com/downloads/

Additional info:

Thanks for the feedback.