Mysql Crash
Any way you could suggest for me to optimize the settings?
MYSQLD.ERR
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.
keybuffersize=33554432
readbuffersize=131072
maxusedconnections=1
max_connections=100
threads_connected=1
It is possible that mysqld could use up to
keybuffersize + (readbuffersize + sortbuffersize)*max_connections = 250367 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=0x4327a628, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x80fb511
0x4015a685
0x8106621
0x40155041
0x4039ab8a
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
The manual page at
information that should help you find out what is causing the crash.
4 Replies
Actual settings:
Those settings should work better with Linode configurations.
Andrew