041025 15:18:10 mysqld started
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=16777216
read_buffer_size=131072
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 80383 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=(nil)
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=0xbfffeee8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x80cf06f
0x40041be5
0x82aef64
0x82aec3f
0x80d271a
0x80d03f2
0x40110936
0x80a48f1
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http ://ww w.my sql.co m/doc/en/Using_stack_trace.h tml and follow instructions on how to resolve the stack trace. Res$
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
The manual page at ht tp ://ww w.mys ql.com/doc/en/Crashing.h tmlcontains
information that should help you find out what is causing the crash.
Number of processes running now: 0
041025 23:07:35 mysqld restarted
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=16777216
read_buffer_size=131072
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 80383 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=(nil)
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=0xbfffeee8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x80cf06f
0x40041be5
0x82aef64
0x82aec3f
0x80d271a
0x80d03f2
0x40110936
0x80a48f1
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http ://ww w.mysql. com/doc/en/Using _stack_tra ce.ht ml and follow instructions on how to resolve the stack trace. Res$
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
The manual page at http ://ww w.my sql.com/do c/en/Crashi ng.ht ml contains
information that should help you find out what is causing the crash.
Bla Bla Bla Bla Bla Bla Bla Bla Bla Bla Bla Bla Bla Bla Bla Bla Bla Bla
-----------------------------------------------------------------------------------
root@www:~# cat /proc/meminfo
total: used: free: shared: buffers: cached:
Mem: 262291456 48783360 213508096 0 10190848 27914240
Swap: 0 0 0
MemTotal: 256144 kB
MemFree: 208504 kB
MemShared: 0 kB
Buffers: 9952 kB
Cached: 27260 kB
SwapCached: 0 kB
Active: 20984 kB
Inactive: 20000 kB
HighTotal: 0 kB
HighFree: 0 kB
LowTotal: 256144 kB
LowFree: 208504 kB
SwapTotal: 0 kB
SwapFree: 0 kB
-----------------------------------------------------------------------------------
what can i do ?
Thank YOu very much
