daemon.log.3:Oct 10 21:31:16 uk2-host2 mysqld[11669]: 061010 21:31:16 InnoDB: Database was not shut down normally! daemon.log.3:Oct 10 21:31:16 uk2-host2 mysqld[11669]: InnoDB: Starting crash recovery. daemon.log.3:Oct 10 21:31:16 uk2-host2 mysqld[11669]: InnoDB: Reading tablespace information from the .ibd files... daemon.log.3:Oct 10 21:31:16 uk2-host2 mysqld[11669]: InnoDB: Restoring possible half-written data pages from the doublewrite daemon.log.3:Oct 10 21:31:16 uk2-host2 mysqld[11669]: InnoDB: buffer... daemon.log.3:Oct 10 21:31:16 uk2-host2 mysqld[11669]: 061010 21:31:16 InnoDB: Starting log scan based on checkpoint at daemon.log.3:Oct 10 21:31:16 uk2-host2 mysqld[11669]: InnoDB: log sequence number 0 29392640. daemon.log.3:Oct 10 21:31:16 uk2-host2 mysqld[11669]: InnoDB: Doing recovery: scanned up to log sequence number 0 29393383 daemon.log.3:Oct 10 21:31:16 uk2-host2 mysqld[11669]: 061010 21:31:16 InnoDB: Starting an apply batch of log records to the database... daemon.log.3:Oct 10 21:31:16 uk2-host2 mysqld[11669]: InnoDB: Progress in percents: 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 daemon.log.3:Oct 10 21:31:17 uk2-host2 mysqld[11669]: InnoDB: Apply batch completed daemon.log.3:Oct 10 21:31:17 uk2-host2 mysqld[11669]: InnoDB: Last MySQL binlog file position 0 1711737, file name ./mysql-bin.000019 daemon.log.3:Oct 10 21:31:17 uk2-host2 mysqld[11669]: 061010 21:31:17 InnoDB: Started; log sequence number 0 29393383 daemon.log.3:Oct 10 21:31:17 uk2-host2 mysqld[11669]: 061010 21:31:17 [Note] Recovering after a crash using mysql-bin daemon.log.3:Oct 10 21:31:17 uk2-host2 mysqld[11669]: 061010 21:31:17 [Note] Starting crash recovery... daemon.log.3:Oct 10 21:31:17 uk2-host2 mysqld[11669]: 061010 21:31:17 [Note] Crash recovery finished. daemon.log.3:Oct 10 21:31:18 uk2-host2 mysqld[11669]: 061010 21:31:18 [Note] /usr/sbin/mysqld: ready for connections. daemon.log.3:Oct 10 21:31:18 uk2-host2 mysqld[11669]: Version: '5.0.24a-Debian_2.dotdeb.0-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Dotdeb Sarge backport daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: mysqld got signal 11; daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: This could be because you hit a bug. It is also possible that this binary daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: or one of the libraries it was linked against is corrupt, improperly built, daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: or misconfigured. This error can also be caused by malfunctioning hardware. daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: We will try our best to scrape up some info that will hopefully help diagnose daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: the problem, but since we have already crashed, something is definitely wrong daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: and this may fail. daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: key_buffer_size=134217728 daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: read_buffer_size=2093056 daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: max_used_connections=34 daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: max_connections=100 daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: threads_connected=33 daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: It is possible that mysqld could use up to daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1154671 K daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: bytes of memory daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: Hope that's ok; if not, decrease some variables in the equation. daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: thd=0x9edb178 daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: Attempting backtrace. You can use the following information to find out daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: where mysqld died. If you see no messages after this, something went daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: terribly wrong... daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: Cannot determine thread, fp=0x6baee6b8, backtrace may not be correct. daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: Stack range sanity check OK, backtrace follows: daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: 0x81ba944 daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: 0xffffe420 daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: (nil) daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: 0x81f899b daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: 0x81f8d11 daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: 0x8143138 daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: 0x81434e5 daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: 0x815893d daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: 0x81fb20d daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: 0x8201bb0 daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: 0x81938d8 daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: 0x819003e daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: 0x81fa50c daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: 0x8201b00 daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: 0x82057d5 daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: 0x8201950 daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: 0x81cf13a daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: 0x8227620 daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: Stack trace seems successful - bottom reached daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: stack trace is much more helpful in diagnosing the problem, so please do daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: resolve it daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: Trying to get some variables. daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: Some pointers may be invalid and cause the dump to abort... daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: thd->query at 0x9f50370 = SELECT *, songs.song_id AS id, (SELECT username FROM song_ratings WHERE song_id=id ORDER BY mod_time DESC LIMIT 1) AS last_rater FROM (select distinct song_id from song_ratings order by mod_time desc limit 10) as recent_ratings JOIN songs USING(song_id) JOIN song_signatures ON songs.best_signature_id=signature_id daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: thd->thread_id=44 daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: The manual page at http://www.mysql.com/doc/en/Crashing.html contains daemon.log.3:Oct 10 22:24:12 uk2-host2 mysqld[11669]: information that should help you find out what is causing the crash.