050615 14:09:48 mysqld started 050615 14:09:48 InnoDB: Started; log sequence number 0 125574 050615 14:09:48 InnoDB: Starting recovery for XA transactions... 050615 14:09:48 InnoDB: 0 transactions in prepared state after recovery 050615 14:09:49 [Note] /usr/local/mysql/bin/mysqld: ready for connections. Version: '5.0.6-beta-standard-log' socket: '/tmp/mysql.sock' port: 3306 MySQL Community Edition - Standard (GPL) 050615 14:10:07 InnoDB: Error: MySQL is freeing a thd InnoDB: though trx->n_mysql_tables_in_use is 2 InnoDB: and trx->mysql_n_tables_locked is 0. TRANSACTION 0 2828, not started, process no 11279, OS thread id 49163 mysql tables in use 2, locked 0 MySQL thread id 3, query id 51 172.16.0.187 bsp len 640; hex 065c6e054440480801000000010000007ffeaf42020000000100000001000000000000000c0b0000ffffffff0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001000000ffffffffffffffff0000000000000000000000008b3a020000000000000000001300000000000000a0fe9c0870069d08000000000000000000000000926c480800000000000000000000000000000000000000000bc000000f2c0000020000000000000000000000000000000f270000000000000000000000000000000000000000000000000000000000000000000000000000000000000a00000000000000e814074001000000000000000000000000000000000000000000000001000000010000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000284e07400000000000000000000000002810084000000000000000000000000000000000000000000000000000000000000000000300000000000000000000000000000000000000cc520840bc020000886c48087800000081f20e00010000000000000000000000000000000000000000000000000000000000000000000000936c4808000000000000000000000000000000000000000000000000000000000000000000000000000000000000000068580840; asc \n D@H B : p lH , ' @ (N @ ( @ R @ lH x lH hX @;InnoDB: Apparent memory corruption: mem dump len 500; hex 02fd000000000000001200000000000000190000000000000000000000000000000000000000000000008100000018c0084098c20840000000009268a520306576616c2e63003c000000000000000000000000000000000000000000000048000000000000000000000048000000400000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000010400000000000000000000000000009268a52078307472782e6300510000000000000000000000000000000000000000000000c00200000000000000000000c00200004000000000000000000000001e8fa9004440480801000000010000007ffeaf42020000000100000001000000000000000c0b0000ffffffff0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001000000ffffffffffffffff0000000000000000000000008b3a020000000000000000001300000000000000a0fe9c0870069d08000000000000000000000000926c48080000; asc @ @ h 0eval.c < H H @ h x0trx.c Q @ D@H B : p lH ; InnoDB: Scanning backward trying to find previous allocated mem blocks Freed mem block at - 64, file x0trx.c, line 81 Freed mem block at - 192, file 0eval.c, line 60 Freed mem block at - 320, file m0re, line 2315 Freed mem block at - 576, file w0ins.c, line 96 Freed mem block at - 1088, file w0ins.c, line 96 Freed mem block at - 1344, file e0cur.c, line 904 Freed mem block at - 1600, file w0ins.c, line 96 Mem block at - 2112, file mysql.c, line 591 Mem block at - 3136, file t0mem.c, line 193 Mem block at - 3648, file 0dict.c, line 3628 InnoDB: Scanning forward trying to find next allocated mem blocks Mem block at + 960, file mysql.c, line 591 Mem block at + 1472, file t0mem.c, line 46 Mem block at + 1984, file t0mem.c, line 46 Freed mem block at + 2880, file m0rec.c, line 1053 Mem block at + 3008, file nodb.cc, line 2931 Mem block at + 4032, file t0mem.c, line 46 Mem block at + 5056, file mysql.c, line 591 Freed mem block at + 6080, file x0trx.c, line 164 Mem block at + 6592, file t0mem.c, line 46 Mem block at + 7104, file mysql.c, line 591 050615 14:10:07InnoDB: Assertion failure in thread 49163 in file ha_innodb.cc line 750 InnoDB: Failing assertion: 0 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/mysql/en/Forcing_recovery.html InnoDB: about forcing recovery. 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. key_buffer_size=16777216 read_buffer_size=258048 max_used_connections=1 max_connections=100 threads_connected=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 92783 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x89cfea0 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=0xbfe5f498, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x8099672 0x83409c8 0x812bd10 0x81323d6 0x8095e3a 0x8095ab8 0x80ca3f1 0x80d7440 0x80d74b8 0x80f46fa 0x8092503 0x8310875 0x808f20f 0x8099280 0x80a7bf8 0x833e17c 0x8367b8a 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 (nil) is invalid pointer thd->thread_id=3 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 050615 14:10:07 mysqld restarted InnoDB: Warning: we did not need to do crash recovery, but log scan InnoDB: progressed past the checkpoint lsn 0 125574 up to lsn 0 146059 050615 14:10:07 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 98 99 InnoDB: Apply batch completed 050615 14:10:08 InnoDB: Started; log sequence number 0 125574 050615 14:10:08 [Note] Recovering after a crash using mysql-bin 050615 14:10:08 [Note] Starting crash recovery... 050615 14:10:08 InnoDB: Starting recovery for XA transactions... 050615 14:10:08 InnoDB: 0 transactions in prepared state after recovery 050615 14:10:08 [Note] Crash recovery finished. 050615 14:10:08 InnoDB: Starting recovery for XA transactions... 050615 14:10:08 InnoDB: 0 transactions in prepared state after recovery 050615 14:10:08 [Note] /usr/local/mysql/bin/mysqld: ready for connections. Version: '5.0.6-beta-standard-log' socket: '/tmp/mysql.sock' port: 3306 MySQL Community Edition - Standard (GPL)