Description:
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=209715200
read_buffer_size=1044480
max_used_connections=249
max_connections=250
threads_connected=210
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 715798
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
You seem to be running 32-bit Linux and have 210 concurrent connections.
If you have not changed STACK_SIZE in LinuxThreads and built the binary
yourself, LinuxThreads is quite likely to steal a part of the global heap for
the thread stack. Please read http://www.mysql.com/doc/L/i/Linux.html
thd=0x8a73d100
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=0x7b8ae33c, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x80db9d4
0x400b6618
0x100
0x837a216
0x8364738
0x835e210
0x835d194
0x835cdbb
0x8131898
0x810a4aa
0x8109217
0x8108d64
0x8108e64
0x8108c3c
0x81008f7
0x80ff596
0x80e6a12
0x80ea455
0x80e5b33
0x80e557e
0x80e4da8
0x400b12b6
0x420de407
???
It's alway occur frequently.. a week.
็้How can I report? or Fix This bug?
Hope you help and be write back.
How to repeat:
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=209715200
read_buffer_size=1044480
max_used_connections=249
max_connections=250
threads_connected=210
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 715798
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
You seem to be running 32-bit Linux and have 210 concurrent connections.
If you have not changed STACK_SIZE in LinuxThreads and built the binary
yourself, LinuxThreads is quite likely to steal a part of the global heap for
the thread stack. Please read http://www.mysql.com/doc/L/i/Linux.html
thd=0x8a73d100
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=0x7b8ae33c, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x80db9d4
0x400b6618
0x100
0x837a216
0x8364738
0x835e210
0x835d194
0x835cdbb
0x8131898
0x810a4aa
0x8109217
0x8108d64
0x8108e64
0x8108c3c
0x81008f7
0x80ff596
0x80e6a12
0x80ea455
0x80e5b33
0x80e557e
0x80e4da8
0x400b12b6
0x420de407
???
It's alway occur frequently.. a week.
็้How can I report? or Fix This bug?
Hope you help and be write back.
