mysqldump死住(实际是导致mysqld crash)

http://tech.ddvip.com   2007年02月13日    社区交流

本文详细介绍mysqldump死住(实际是导致mysqld crash)

  在MySQL 5.0.16上,用mysqldump导出数据,mysqldump半天没反应。

  操作系统是RHEL4.0。

  看日志

  *** glibc detected *** free(): invalid pointer: 0xb17d60b0 ***

  mysqld got signal 6;

  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=8388600

  read_buffer_size=131072

  max_used_connections=2

  max_connections=100

  threads_connected=2

  It is possible that mysqld could use up to

  key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225791 K

  bytes of memory

  Hope that's ok; if not, decrease some variables in the equation.

  thd=0x9d69ba0

  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=0xb17d5a6c, backtrace may not be correct.

  Stack range sanity check OK, backtrace follows:

  0x815f652

  0x9ed7c8

  (nil)

  0x81d40a

  0x823b3f

  0x823eba

  0x819eb85

  0x819f5bf

  0x819f7f9

  0x82314e9

  0x8178872

  0x817db98

  0x817e59c

  0x817f99c

  0x9e7341

  0x8896fe

  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 0x9d7bb00 = show create table `T_SOD_BEHAVIORRECORD_VIEW`

  thd->thread_id=7

  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.

  Number of processes running now: 0

  070119 15:58:48 mysqld restarted

  mysqldump导致mysqld崩溃了,这个现象在源码安装和rpm安装的MySQL5.0.16上都出现了。换成5.0.19就好了。查了一下bug:

  Bug #14726 Crash when mysqldump encounters a view while privileges limited.

  如果用视图的话,至少要用5.0.17以上版本了

责编:豆豆技术应用

正在加载评论...