程序師世界是廣大編程愛好者互助、分享、學習的平台,程序師世界有你更精彩!
首頁
編程語言
C語言|JAVA編程
Python編程
網頁編程
ASP編程|PHP編程
JSP編程
數據庫知識
MYSQL數據庫|SqlServer數據庫
Oracle數據庫|DB2數據庫
 程式師世界 >> 數據庫知識 >> MYSQL數據庫 >> 關於MYSQL數據庫 >> mysqldump死住(實際是導致mysqld crash)

mysqldump死住(實際是導致mysqld crash)

編輯:關於MYSQL數據庫

  在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以上版本了

  1. 上一頁:
  2. 下一頁:
Copyright © 程式師世界 All Rights Reserved