Apr 14 14:37:18 db-14 mysqld[8650]: mysqld got signal 11;
Apr 14 14:37:18 db-14 mysqld[8650]: This could be because you hit a bug. It is also possible that this binary
Apr 14 14:37:18 db-14 mysqld[8650]: or one of the libraries it was linked against is corrupt, improperly built,
Apr 14 14:37:18 db-14 mysqld[8650]: or misconfigured. This error can also be caused by malfunctioning hardware.
Apr 14 14:37:18 db-14 mysqld[8650]: We will try our best to scrape up some info that will hopefully help diagnose
Apr 14 14:37:18 db-14 mysqld[8650]: the problem, but since we have already crashed, something is definitely wrong
Apr 14 14:37:18 db-14 mysqld[8650]: and this may fail.
Apr 14 14:37:18 db-14 mysqld[8650]: 
Apr 14 14:37:18 db-14 mysqld[8650]: key_buffer_size=8388608
Apr 14 14:37:18 db-14 mysqld[8650]: read_buffer_size=2093056
Apr 14 14:37:18 db-14 mysqld[8650]: max_used_connections=471
Apr 14 14:37:18 db-14 mysqld[8650]: max_connections=800
Apr 14 14:37:18 db-14 mysqld[8650]: threads_connected=242
Apr 14 14:37:18 db-14 mysqld[8650]: It is possible that mysqld could use up to 
Apr 14 14:37:18 db-14 mysqld[8650]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 3281785 K
Apr 14 14:37:18 db-14 mysqld[8650]: bytes of memory
Apr 14 14:37:18 db-14 mysqld[8650]: Hope that's ok; if not, decrease some variables in the equation.
Apr 14 14:37:18 db-14 mysqld[8650]: 
Apr 14 14:37:18 db-14 mysqld[8650]: thd=0x2aaaaeca3460
Apr 14 14:37:18 db-14 mysqld[8650]: Attempting backtrace. You can use the following information to find out
Apr 14 14:37:18 db-14 mysqld[8650]: where mysqld died. If you see no messages after this, something went
Apr 14 14:37:18 db-14 mysqld[8650]: terribly wrong...
Apr 14 14:37:18 db-14 mysqld[8650]: Cannot determine thread, fp=0x45a6f190, backtrace may not be correct.
Apr 14 14:37:18 db-14 mysqld[8650]: Stack range sanity check OK, backtrace follows:
Apr 14 14:37:18 db-14 mysqld[8650]: (nil)
Apr 14 14:37:18 db-14 mysqld[8650]: Stack trace seems successful - bottom reached
Apr 14 14:37:18 db-14 mysqld[8650]: Please read http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow instructions on how to reso
lve the stack trace. Resolved
Apr 14 14:37:18 db-14 mysqld[8650]: stack trace is much more helpful in diagnosing the problem, so please do 
Apr 14 14:37:18 db-14 mysqld[8650]: resolve it
Apr 14 14:37:18 db-14 mysqld[8650]: Trying to get some variables.
Apr 14 14:37:18 db-14 mysqld[8650]: Some pointers may be invalid and cause the dump to abort...
Apr 14 14:37:18 db-14 mysqld[8650]: thd->query at 0xcb2d3b0 = XA COMMIT 0x31353331323034373639343232323536373034,0x31,0x9913
Apr 14 14:37:18 db-14 mysqld[8650]: thd->thread_id=24833
Apr 14 14:37:18 db-14 mysqld[8650]: The manual page at http://www.mysql.com/doc/en/Crashing.html contains
Apr 14 14:37:18 db-14 mysqld[8650]: information that should help you find out what is causing the crash.
Apr 14 14:37:18 db-14 mysqld_safe[32125]: Number of processes running now: 0
Apr 14 14:37:18 db-14 mysqld_safe[32127]: restarted
Apr 14 14:37:19 db-14 mysqld[32130]: 070414 14:37:19  InnoDB: Database was not shut down normally!
Apr 14 14:37:19 db-14 mysqld[32130]: InnoDB: Starting crash recovery.
Apr 14 14:37:19 db-14 mysqld[32130]: InnoDB: Reading tablespace information from the .ibd files...
Apr 14 14:37:19 db-14 mysqld[32130]: InnoDB: Restoring possible half-written data pages from the doublewrite
Apr 14 14:37:19 db-14 mysqld[32130]: InnoDB: buffer...
Apr 14 14:37:19 db-14 mysqld[32130]: 070414 14:37:19  InnoDB: Starting log scan based on checkpoint at
Apr 14 14:37:19 db-14 mysqld[32130]: InnoDB: log sequence number 43 854354481.
Apr 14 14:37:20 db-14 mysqld[32130]: InnoDB: Doing recovery: scanned up to log sequence number 43 859597312
Apr 14 14:37:20 db-14 mysqld[32130]: InnoDB: Doing recovery: scanned up to log sequence number 43 864840192
Apr 14 14:37:20 db-14 mysqld[32130]: InnoDB: Doing recovery: scanned up to log sequence number 43 870083072
Apr 14 14:37:21 db-14 mysqld[32130]: InnoDB: Doing recovery: scanned up to log sequence number 43 875325952
Apr 14 14:37:21 db-14 mysqld[32130]: InnoDB: Doing recovery: scanned up to log sequence number 43 880568832
Apr 14 14:37:22 db-14 mysqld[32130]: InnoDB: Doing recovery: scanned up to log sequence number 43 885811712
Apr 14 14:37:22 db-14 mysqld[32130]: InnoDB: Doing recovery: scanned up to log sequence number 43 891054592
Apr 14 14:37:23 db-14 mysqld[32130]: InnoDB: Doing recovery: scanned up to log sequence number 43 896297472
Apr 14 14:37:23 db-14 mysqld[32130]: InnoDB: Doing recovery: scanned up to log sequence number 43 901540352
Apr 14 14:37:23 db-14 mysqld[32130]: InnoDB: Doing recovery: scanned up to log sequence number 43 906783232
Apr 14 14:37:24 db-14 mysqld[32130]: InnoDB: Doing recovery: scanned up to log sequence number 43 912026112
Apr 14 14:37:25 db-14 mysqld[32130]: InnoDB: Doing recovery: scanned up to log sequence number 43 917268992
Apr 14 14:37:25 db-14 mysqld[32130]: InnoDB: Doing recovery: scanned up to log sequence number 43 922511872
Apr 14 14:37:26 db-14 mysqld[32130]: InnoDB: Doing recovery: scanned up to log sequence number 43 927754752
Apr 14 14:37:26 db-14 mysqld[32130]: InnoDB: Doing recovery: scanned up to log sequence number 43 932997632
Apr 14 14:37:27 db-14 mysqld[32130]: InnoDB: Doing recovery: scanned up to log sequence number 43 938240512
Apr 14 14:37:27 db-14 mysqld[32130]: InnoDB: Doing recovery: scanned up to log sequence number 43 943483392
Apr 14 14:37:28 db-14 mysqld[32130]: InnoDB: Doing recovery: scanned up to log sequence number 43 948726272
Apr 14 14:37:29 db-14 mysqld[32130]: InnoDB: Doing recovery: scanned up to log sequence number 43 953969152
Apr 14 14:37:29 db-14 mysqld[32130]: InnoDB: Doing recovery: scanned up to log sequence number 43 959212032
Apr 14 14:37:30 db-14 mysqld[32130]: InnoDB: Doing recovery: scanned up to log sequence number 43 964443187
Apr 14 14:37:30 db-14 mysqld[32130]: InnoDB: Transaction 0 2386163453 was in the XA prepared state.
Apr 14 14:37:30 db-14 mysqld[32130]: InnoDB: Transaction 0 2386163435 was in the XA prepared state.
Apr 14 14:37:30 db-14 mysqld[32130]: InnoDB: 5 transaction(s) which must be rolled back or cleaned up
Apr 14 14:37:30 db-14 mysqld[32130]: InnoDB: in total 7 row operations to undo
Apr 14 14:37:30 db-14 mysqld[32130]: InnoDB: Trx id counter is 0 2386163968
Apr 14 14:37:30 db-14 mysqld[32130]: 070414 14:37:30  InnoDB: Starting an apply batch of log records to the database...
Apr 14 14:40:12 db-14 snmpd[9264]: Connection from UDP: [172.19.0.67]:51565
Apr 14 14:40:12 db-14 snmpd[9264]: Connection from UDP: [172.19.0.67]:51565
Apr 14 14:40:44 db-14 mysqld[32130]: 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 7
6 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
Apr 14 14:40:44 db-14 mysqld[32130]: InnoDB: Apply batch completed
Apr 14 14:40:44 db-14 mysqld[32130]: InnoDB: Last MySQL binlog file position 0 22242676, file name /home/ddb/mysql-5.0/log/mysql-bin.001011
Apr 14 14:40:44 db-14 mysqld[32130]: InnoDB: Starting in background the rollback of uncommitted transactions
Apr 14 14:40:44 db-14 mysqld[32130]: 070414 14:40:44  InnoDB: Rolling back trx with id 0 2386163467, 1 rows to undo
Apr 14 14:40:44 db-14 mysqld[32130]: 070414 14:40:44  InnoDB: Started; log sequence number 43 964443187
Apr 14 14:40:44 db-14 mysqld[32130]: 070414 14:40:44 [Note] Recovering after a crash using /home/ddb/mysql-5.0/log/mysql-bin
Apr 14 14:40:44 db-14 mysqld[32130]: 
Apr 14 14:40:44 db-14 mysqld[32130]: InnoDB: Rolling back of trx id 0 2386163467 completed
Apr 14 14:40:44 db-14 mysqld[32130]: 070414 14:40:44  InnoDB: Rolling back trx with id 0 2386162978, 2 rows to undo
Apr 14 14:40:44 db-14 mysqld[32130]: 
Apr 14 14:40:44 db-14 mysqld[32130]: InnoDB: Rolling back of trx id 0 2386162978 completed
Apr 14 14:40:44 db-14 mysqld[32130]: 070414 14:40:44  InnoDB: Rolling back trx with id 0 2386162797, 4 rows to undo
Apr 14 14:40:44 db-14 mysqld[32130]: 070414 14:40:44 [Note] Starting crash recovery...
Apr 14 14:40:44 db-14 mysqld[32130]: 070414 14:40:44  InnoDB: Starting recovery for XA transactions...
Apr 14 14:40:44 db-14 mysqld[32130]: 070414 14:40:44  InnoDB: Transaction 0 2386163453 in prepared state after recovery
Apr 14 14:40:44 db-14 mysqld[32130]: 070414 14:40:44  InnoDB: Transaction contains changes to 1 rows
Apr 14 14:40:44 db-14 mysqld[32130]: 070414 14:40:44  InnoDB: Transaction 0 2386163435 in prepared state after recovery
Apr 14 14:40:44 db-14 mysqld[32130]: 070414 14:40:44  InnoDB: Transaction contains changes to 2 rows
Apr 14 14:40:44 db-14 mysqld[32130]: 070414 14:40:44  InnoDB: 2 transactions in prepared state after recovery
Apr 14 14:40:44 db-14 mysqld[32130]: 070414 14:40:44 [Note] Found 2 prepared transaction(s) in InnoDB
Apr 14 14:40:44 db-14 mysqld[32130]: 070414 14:40:44 [Warning] Found 2 prepared XA transactions
Apr 14 14:40:44 db-14 mysqld[32130]: 070414 14:40:44 [Note] Crash recovery finished.
Apr 14 14:40:44 db-14 mysqld[32130]: 070414 14:40:44  InnoDB: Starting recovery for XA transactions...
Apr 14 14:40:44 db-14 mysqld[32130]: 070414 14:40:44  InnoDB: Transaction 0 2386163453 in prepared state after recovery
Apr 14 14:40:44 db-14 mysqld[32130]: 070414 14:40:44  InnoDB: Transaction contains changes to 1 rows
Apr 14 14:40:44 db-14 mysqld[32130]: 070414 14:40:44  InnoDB: Transaction 0 2386163435 in prepared state after recovery
Apr 14 14:40:44 db-14 mysqld[32130]: 070414 14:40:44  InnoDB: Transaction contains changes to 2 rows
Apr 14 14:40:44 db-14 mysqld[32130]: 070414 14:40:44  InnoDB: 2 transactions in prepared state after recovery
Apr 14 14:40:44 db-14 mysqld[32130]: 070414 14:40:44 [Note] Found 2 prepared transaction(s) in InnoDB
Apr 14 14:40:44 db-14 mysqld[32130]: 070414 14:40:44 [Warning] Found 2 prepared XA transactions
Apr 14 14:40:44 db-14 mysqld[32130]: 
Apr 14 14:40:44 db-14 mysqld[32130]: InnoDB: Rolling back of trx id 0 2386162797 completed
Apr 14 14:40:44 db-14 mysqld[32130]: 070414 14:40:44  InnoDB: Rollback of non-prepared transactions completed
Apr 14 14:40:44 db-14 mysqld[32130]: 070414 14:40:44 [Note] /usr/sbin/mysqld: ready for connections.
Apr 14 14:40:44 db-14 mysqld[32130]: Version: '5.0.30-Debian_1-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 4330  Debian etch distributio
n