051210 9:08:54 [Note] /usr/local/mysql/bin/mysqld: ready for connections. Version: '5.0.16-standard-log' socket: '/tmp/mysql_devel.sock' port: 3306 MySQL Community Edition - Standard (GPL) len 112; hex 684751b75f8162af0000000000000000030000000100000001000000000000000000000003000000000000000000000000000000000000000100000083445107edfe50b70100000003000000a0df22af000000000000000060e1117702000000681451b700000000e8fe50b709000000; asc hGQ _ b DQ P " ` w h Q P ;TRANSACTION 0 2690319, ACTIVE 0 sec, process no 5619, OS thread id 2786331568 unlock_row mysql tables in use 2, locked 2 4 lock struct(s), heap size 320 MySQL thread id 18, query id 167 localhost 127.0.0.1 root Sending data DELETE ml.* FROM mail_l AS ml LEFT JOIN mail_mails AS mm ON (mm.id=ml.mail_id) WHERE mm.id IS NULL 051210 9:09:17InnoDB: Assertion failure in thread 2786331568 in file btr0pcur.c line 216 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=67108864 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 = 283135 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x8a46d88 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=0xa613ef7c, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x8150650 0xffffe420 0x1 0x81f62c5 0x819bebf 0x8195cda 0x819be75 0x8195cda 0x819bb28 0x8191ed2 0x81929f5 0x8167ed2 Stack trace seems successful - bottom reached 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 0x8a4c208 = DELETE ml.* FROM mail_l AS ml LEFT JOIN mail_mails AS mm ON (mm.id=ml.mail_id) WHERE mm.id IS NULL thd->thread_id=18 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 051210 09:09:17 mysqld restarted 051210 9:09:18 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... 051210 9:09:18 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 6 272904765. InnoDB: Doing recovery: scanned up to log sequence number 6 272904765 InnoDB: Last MySQL binlog file position 0 228, file name ./log-bin.000015 051210 9:09:18 InnoDB: Started; log sequence number 6 272904765 051210 9:09:18 [Note] Recovering after a crash using log-bin 051210 9:09:18 [Note] Starting crash recovery... 051210 9:09:18 [Note] Crash recovery finished. 051210 9:09:18 [Note] /usr/local/mysql/bin/mysqld: ready for connections. Version: '5.0.16-standard-log' socket: '/tmp/mysql_devel.sock' port: 3306 MySQL Community Edition - Standard (GPL)