All pastes #829046 Raw Edit

Untitled

public text v1 · immutable
#829046 ·published 2007-12-22 21:54 UTC
rendered paste body
Dec 22 22:53:35 ns22486 mysqld_safe[11405]: started
Dec 22 22:53:35 ns22486 mysqld[11409]: 071222 22:53:35  InnoDB: Database was not shut down normally!
Dec 22 22:53:35 ns22486 mysqld[11409]: InnoDB: Starting crash recovery.
Dec 22 22:53:35 ns22486 mysqld[11409]: InnoDB: Reading tablespace information from the .ibd files...
Dec 22 22:53:35 ns22486 mysqld[11409]: InnoDB: Restoring possible half-written data pages from the doublewrite
Dec 22 22:53:35 ns22486 mysqld[11409]: InnoDB: buffer...
Dec 22 22:53:35 ns22486 mysqld[11409]: 071222 22:53:35  InnoDB: Starting log scan based on checkpoint at
Dec 22 22:53:35 ns22486 mysqld[11409]: InnoDB: log sequence number 6 4143841883.
Dec 22 22:53:35 ns22486 mysqld[11409]: InnoDB: Doing recovery: scanned up to log sequence number 6 4143867075
Dec 22 22:53:35 ns22486 mysqld[11409]: 071222 22:53:35  InnoDB: Starting an apply batch of log records to the database...
Dec 22 22:53:35 ns22486 mysqld[11409]: InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 071222 22:53:35 - mysqld got signal 11;
Dec 22 22:53:35 ns22486 mysqld[11409]: This could be because you hit a bug. It is also possible that this binary
Dec 22 22:53:35 ns22486 mysqld[11409]: or one of the libraries it was linked against is corrupt, improperly built,
Dec 22 22:53:35 ns22486 mysqld[11409]: or misconfigured. This error can also be caused by malfunctioning hardware.
Dec 22 22:53:35 ns22486 mysqld[11409]: We will try our best to scrape up some info that will hopefully help diagnose
Dec 22 22:53:35 ns22486 mysqld[11409]: the problem, but since we have already crashed, something is definitely wrong
Dec 22 22:53:35 ns22486 mysqld[11409]: and this may fail.
Dec 22 22:53:35 ns22486 mysqld[11409]:
Dec 22 22:53:35 ns22486 mysqld[11409]: key_buffer_size=0
Dec 22 22:53:35 ns22486 mysqld[11409]: read_buffer_size=131072
Dec 22 22:53:35 ns22486 mysqld[11409]: max_used_connections=0
Dec 22 22:53:35 ns22486 mysqld[11409]: max_connections=100
Dec 22 22:53:35 ns22486 mysqld[11409]: threads_connected=0
Dec 22 22:53:35 ns22486 mysqld[11409]: It is possible that mysqld could use up to
Dec 22 22:53:35 ns22486 mysqld[11409]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 217599 K
Dec 22 22:53:35 ns22486 mysqld[11409]: bytes of memory
Dec 22 22:53:35 ns22486 mysqld[11409]: Hope that's ok; if not, decrease some variables in the equation.
Dec 22 22:53:35 ns22486 mysqld[11409]:
Dec 22 22:53:35 ns22486 mysqld[11409]: thd=(nil)
Dec 22 22:53:35 ns22486 mysqld[11409]: Attempting backtrace. You can use the following information to find out
Dec 22 22:53:35 ns22486 mysqld[11409]: where mysqld died. If you see no messages after this, something went
Dec 22 22:53:35 ns22486 mysqld[11409]: terribly wrong...
Dec 22 22:53:35 ns22486 mysqld[11409]: Cannot determine thread, fp=0x71b6b458, backtrace may not be correct.
Dec 22 22:53:35 ns22486 mysqld[11409]: Stack range sanity check OK, backtrace follows:
Dec 22 22:53:35 ns22486 mysqld[11409]: 0x81ca48d
Dec 22 22:53:35 ns22486 mysqld[11409]: 0x83e2ef2
Dec 22 22:53:35 ns22486 mysqld[11409]: 0x83e3b7b
Dec 22 22:53:35 ns22486 mysqld[11409]: 0x83a76d5
Dec 22 22:53:35 ns22486 mysqld[11409]: 0x83a95e0
Dec 22 22:53:35 ns22486 mysqld[11409]: 0x839684a
Dec 22 22:53:35 ns22486 mysqld[11409]: 0x83c1bfc
Dec 22 22:53:35 ns22486 mysqld[11409]: 0x83076e8
Dec 22 22:53:35 ns22486 mysqld[11409]: 0xb7fa40bd
Dec 22 22:53:35 ns22486 mysqld[11409]: 0xb7ddeace
Dec 22 22:53:35 ns22486 mysqld[11409]: New value of fp=(nil) failed sanity check, terminating stack trace!
Dec 22 22:53:35 ns22486 mysqld[11409]: Please read http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow instructions on how to resolve the stack trace. Resolved
Dec 22 22:53:35 ns22486 mysqld[11409]: stack trace is much more helpful in diagnosing the problem, so please do
Dec 22 22:53:35 ns22486 mysqld[11409]: resolve it
Dec 22 22:53:35 ns22486 mysqld[11409]: The manual page at http://www.mysql.com/doc/en/Crashing.html contains
Dec 22 22:53:35 ns22486 mysqld[11409]: information that should help you find out what is causing the crash.
Dec 22 22:53:35 ns22486 mysqld_safe[11415]: ended