Description:
MySql has crash (and in next 1 hour have [maybe by mysql] server upload 100GB+)
Distrib 5.0.20a
logs:
Jun 14 06:25:40 localhost mysqld[10883]: mysqld got signal 11;
Jun 14 06:25:40 localhost mysqld[10883]: This could be because you hit a bug. It is also possible that this binary
Jun 14 06:25:40 localhost mysqld[10883]: or one of the libraries it was linked against is corrupt, improperly built,
Jun 14 06:25:40 localhost mysqld[10883]: or misconfigured. This error can also be caused by malfunctioning hardware.
Jun 14 06:25:40 localhost mysqld[10883]: We will try our best to scrape up some info that will hopefully help diagnose
Jun 14 06:25:40 localhost mysqld[10883]: the problem, but since we have already crashed, something is definitely wrong
Jun 14 06:25:40 localhost mysqld[10883]: and this may fail.
Jun 14 06:25:40 localhost mysqld[10883]:
Jun 14 06:25:40 localhost mysqld[10883]: key_buffer_size=16777216
Jun 14 06:25:40 localhost mysqld[10883]: read_buffer_size=131072
Jun 14 06:25:40 localhost mysqld[10883]: max_used_connections=72
Jun 14 06:25:40 localhost mysqld[10883]: max_connections=100
Jun 14 06:25:40 localhost mysqld[10883]: threads_connected=33
Jun 14 06:25:40 localhost mysqld[10883]: It is possible that mysqld could use up to
Jun 14 06:25:40 localhost mysqld[10883]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 233983 K
Jun 14 06:25:40 localhost mysqld[10883]: bytes of memory
Jun 14 06:25:40 localhost mysqld[10883]: Hope that's ok; if not, decrease some variables in the equation.
Jun 14 06:25:40 localhost mysqld[10883]:
Jun 14 06:25:40 localhost mysqld[10883]: thd=0x44fcec70
Jun 14 06:25:40 localhost mysqld[10883]: Attempting backtrace. You can use the following information to find out
Jun 14 06:25:40 localhost mysqld[10883]: where mysqld died. If you see no messages after this, something went
Jun 14 06:25:40 localhost mysqld[10883]: terribly wrong...
Jun 14 06:25:40 localhost mysqld[10883]: Cannot determine thread, fp=0x44549158, backtrace may not be correct.
Jun 14 06:25:40 localhost mysqld[10883]: Stack range sanity check OK, backtrace follows:
Jun 14 06:25:40 localhost mysqld[10883]: 0x81916fc
Jun 14 06:25:40 localhost mysqld[10883]: 0x4005ad26
Jun 14 06:25:40 localhost mysqld[10883]: 0x844ecf9
Jun 14 06:25:40 localhost mysqld[10883]: 0x8201c6b
Jun 14 06:25:40 localhost mysqld[10883]: 0x820483c
Jun 14 06:25:40 localhost mysqld[10883]: 0x82059d7
Jun 14 06:25:40 localhost mysqld[10883]: 0x81a074a
Jun 14 06:25:40 localhost mysqld[10883]: 0x81aba97
Jun 14 06:25:40 localhost mysqld[10883]: 0x81ac6a8
Jun 14 06:25:40 localhost mysqld[10883]: 0x81acff4
Jun 14 06:25:40 localhost mysqld[10883]: 0x40054c37
Jun 14 06:25:40 localhost mysqld[10883]: 0x402b82ba
Jun 14 06:25:40 localhost mysqld[10883]: New value of fp=(nil) failed sanity check, terminating stack trace!
Jun 14 06:25:40 localhost mysqld[10883]: Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved
Jun 14 06:25:40 localhost mysqld[10883]: stack trace is much more helpful in diagnosing the problem, so please do
Jun 14 06:25:40 localhost mysqld[10883]: resolve it
Jun 14 06:25:40 localhost mysqld[10883]: Trying to get some variables.
Jun 14 06:25:40 localhost mysqld[10883]: Some pointers may be invalid and cause the dump to abort...
Jun 14 06:25:40 localhost mysqld[10883]: thd->query at (nil) is invalid pointer
Jun 14 06:25:40 localhost mysqld[10883]: thd->thread_id=285326
Jun 14 06:25:40 localhost mysqld[10883]: The manual page at http://www.mysql.com/doc/en/Crashing.html contains
Jun 14 06:25:40 localhost mysqld[10883]: information that should help you find out what is causing the crash.
Jun 14 06:25:42 localhost mysqld_safe[16677]: Number of processes running now: 0
Jun 14 06:25:42 localhost mysqld_safe[16679]: restarted
and some problem with mysql logs...
How to repeat:
unkown bug
