RootForum Community

Code: Select all

# 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=1149231104
read_buffer_size=131072
max_used_connections=16
max_connections=512
threads_connected=3
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 2236404 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0xb7e05eb8
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=0xbe5fdb78, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x8147210
0x40039a0d
0x8389967
0x81d621f
0x815b79d
0x815ee2e
0x8158545
0x815818a
0x8157999
0x4003325b
0x401a3cca
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 0x8a02aa8 = drop database djctest01
thd->thread_id=23568
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.

Code: Select all

mysql > use database;
Database changed
mysql > drop database database2;

Code: Select all

max_connections=512
key_buffer_size=1149235192

Code: Select all

--language=..../german