Bug #21709 mysql server crashing
Submitted: 18 Aug 2006 5:12 Modified: 18 Sep 2006 11:40
Reporter: Janno Rütter Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S2 (Serious)
Version:5.0.24-0 OS:
Assigned to: MySQL Verification Team CPU Architecture:Any
Tags: Linux 2.6.12-1.1378 Fedora Core 3

[18 Aug 2006 5:12] Janno Rütter
Description:
Latest version of MySQL is crashing all the time. MySQL-server-5.0.24-0 with MySQL-Max-5.0.24-0 give error+log like this:

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=536870912
read_buffer_size=67104768
max_used_connections=48
max_connections=75
threads_connected=47
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1965779 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x8b9ec380
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...
Cannot determine thread, fp=0x26abf4, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x8176da7
0x664420
0x26b1e0
0x816be39
0x81769c2
0x8186a42
0x28d341
0xca3fee
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at (nil)  is invalid pointer
thd->thread_id=216
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.

I try to make stack-trace and it gives this result:

resolve_stack_dump -s /usr/lib/mysql/mysqld-max.sym -n mysqld.stack
0x8176da7 handle_segfault + 423
0x8a7420 (?)
0x4b0c1e0 (?)
0x816be39 cleanup__3THD + 169
0x81769c2 end_thread__FP3THDb + 18
0x8186a42 handle_one_connection + 1074
0x28d341 (?)
0xca3fee (?)

resolve_stack_dump -s /usr/lib/mysql/mysqld.sym -n mysqld.stack
0x8176da7 mysql_reconnect + 87
0x8a7420 (?)
0x4b0c1e0 (?)
0x816be39 show_master_info__FP3THDP14st_master_info + 4969
0x81769c2 mysql_real_connect + 2626
0x8186a42 create_typelib__FP11st_mem_rootP12create_fieldPt4List1Z6String + 194
0x28d341 (?)
0xca3fee (?)

MySQL-server-5.0.22-0 with MySQL-Max-5.0.22-0 works with no errors.

How to repeat:
I don't now how to repeat it.
[18 Aug 2006 11:40] MySQL Verification Team
Thank you for the bug report. We need a repeatable test case, if possible
for you to enable the log query for to try to find which query is the source
of the crash? and then then try to repeat?

Thanks in advance.
[18 Sep 2006 23:00] Bugs System
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".