Description:
061128 11:25:25 [Warning] Warning: Enabling keys got errno 127, retrying
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=524288000
read_buffer_size=134213632
max_used_connections=9
max_connections=100
threads_connected=9
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1240687 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x8f935f18
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=0x1d329c, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x81d9210
0xb5a7c8
0x36373732
0x8413511
0x8294a29
0x8234eba
0x8234a15
0x8227081
0x8222d39
0x8225dce
0x8221f9d
0x81f21cd
0x81f9abb
0x81f07e3
0x81f032d
0x81ef85f
0xb54341
0x8bc6fe
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 0x8f304490 is invalid pointer
thd->thread_id=524
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.
Number of processes running now: 0
How to repeat:
See private comment. It did not occur again when running the SELECT.
Suggested fix:
No idea.
