daemon.log.3:Oct  9 09:10:58 uk2-host2 mysqld[28311]: 061009  9:10:58  InnoDB: Database was not shut down normally!
daemon.log.3:Oct  9 09:10:58 uk2-host2 mysqld[28311]: InnoDB: Starting crash recovery.
daemon.log.3:Oct  9 09:10:58 uk2-host2 mysqld[28311]: InnoDB: Reading tablespace information from the .ibd files...
daemon.log.3:Oct  9 09:10:58 uk2-host2 mysqld[28311]: InnoDB: Restoring possible half-written data pages from the doublewrite
daemon.log.3:Oct  9 09:10:58 uk2-host2 mysqld[28311]: InnoDB: buffer...
daemon.log.3:Oct  9 09:10:58 uk2-host2 mysqld[28311]: 061009  9:10:58  InnoDB: Starting log scan based on checkpoint at
daemon.log.3:Oct  9 09:10:58 uk2-host2 mysqld[28311]: InnoDB: log sequence number 0 25066467.
daemon.log.3:Oct  9 09:10:58 uk2-host2 mysqld[28311]: InnoDB: Doing recovery: scanned up to log sequence number 0 25066887
daemon.log.3:Oct  9 09:10:58 uk2-host2 mysqld[28311]: 061009  9:10:58  InnoDB: Starting an apply batch of log records to the database...
daemon.log.3:Oct  9 09:10:59 uk2-host2 mysqld[28311]: 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  9 09:10:59 uk2-host2 mysqld[28311]: InnoDB: Apply batch completed
daemon.log.3:Oct  9 09:10:59 uk2-host2 mysqld[28311]: InnoDB: Last MySQL binlog file position 0 52306, file name ./mysql-bin.000017
daemon.log.3:Oct  9 09:10:59 uk2-host2 mysqld[28311]: 061009  9:10:59  InnoDB: Started; log sequence number 0 25066887
daemon.log.3:Oct  9 09:10:59 uk2-host2 mysqld[28311]: 061009  9:10:59 [Note] Recovering after a crash using mysql-bin
daemon.log.3:Oct  9 09:10:59 uk2-host2 mysqld[28311]: 061009  9:10:59 [Note] Starting crash recovery...
daemon.log.3:Oct  9 09:10:59 uk2-host2 mysqld[28311]: 061009  9:10:59 [Note] Crash recovery finished.
daemon.log.3:Oct  9 09:11:01 uk2-host2 mysqld[28311]: 061009  9:11:01 [Note] /usr/sbin/mysqld: ready for connections.
daemon.log.3:Oct  9 09:11:01 uk2-host2 mysqld[28311]: Version: '5.0.24a-Debian_2.dotdeb.0-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  Dotdeb Sarge backport
daemon.log.3:Oct  9 18:36:34 uk2-host2 mysqld[28311]: 061009 18:36:34 [ERROR] /usr/sbin/mysqld: Table './wordpress/19999994444_options' is marked as crashed and should be repaired
daemon.log.3:Oct  9 18:36:34 uk2-host2 mysqld[28311]: 061009 18:36:34 [Warning] Checking table:   './wordpress/19999994444_options'
daemon.log.3:Oct  9 18:36:34 uk2-host2 mysqld[28311]: 061009 18:36:34 [ERROR] /usr/sbin/mysqld: Table './wordpress/19999994444_comments' is marked as crashed and should be repaired
daemon.log.3:Oct  9 18:36:34 uk2-host2 mysqld[28311]: 061009 18:36:34 [Warning] Checking table:   './wordpress/19999994444_comments'
daemon.log.3:Oct  9 18:36:34 uk2-host2 mysqld[28311]: 061009 18:36:34 [ERROR] /usr/sbin/mysqld: Table './wordpress/19999994444_sk2_spams' is marked as crashed and should be repaired
daemon.log.3:Oct  9 18:36:34 uk2-host2 mysqld[28311]: 061009 18:36:34 [Warning] Checking table:   './wordpress/19999994444_sk2_spams'
daemon.log.3:Oct  9 18:36:34 uk2-host2 mysqld[28311]: 061009 18:36:34 [ERROR] /usr/sbin/mysqld: Table './wordpress/sk2_blacklist' is marked as crashed and should be repaired
daemon.log.3:Oct  9 18:36:34 uk2-host2 mysqld[28311]: 061009 18:36:34 [Warning] Checking table:   './wordpress/sk2_blacklist'
daemon.log.3:Oct  9 18:36:34 uk2-host2 mysqld[28311]: 061009 18:36:34 [ERROR] /usr/sbin/mysqld: Table './wordpress/19999994444_sk2_logs' is marked as crashed and should be repaired
daemon.log.3:Oct  9 18:36:34 uk2-host2 mysqld[28311]: 061009 18:36:34 [Warning] Checking table:   './wordpress/19999994444_sk2_logs'
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: mysqld got signal 11;
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: This could be because you hit a bug. It is also possible that this binary
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: or one of the libraries it was linked against is corrupt, improperly built,
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: or misconfigured. This error can also be caused by malfunctioning hardware.
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: We will try our best to scrape up some info that will hopefully help diagnose
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: the problem, but since we have already crashed, something is definitely wrong
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: and this may fail.
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: 
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: key_buffer_size=134217728
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: read_buffer_size=2093056
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: max_used_connections=30
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: max_connections=100
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: threads_connected=29
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: It is possible that mysqld could use up to 
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1154671 K
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: bytes of memory
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: Hope that's ok; if not, decrease some variables in the equation.
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: 
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: thd=0x9f4e950
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: Attempting backtrace. You can use the following information to find out
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: where mysqld died. If you see no messages after this, something went
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: terribly wrong...
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: Cannot determine thread, fp=0x60d216b8, backtrace may not be correct.
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: Stack range sanity check OK, backtrace follows:
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: 0x81ba944
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: 0xffffe420
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: (nil)
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: 0x81f899b
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: 0x81f8d11
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: 0x8143138
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: 0x81434e5
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: 0x815893d
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: 0x81fb20d
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: 0x8201bb0
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: 0x81938d8
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: 0x819003e
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: 0x81fa50c
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: 0x8201b00
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: 0x82057d5
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: 0x8201950
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: 0x81cf13a
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: 0x8227620
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: 0x82263ea
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: 0x81ce7fd
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: 0x81cd37d
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: 0x81cc812
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: 0xb7f22b63
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: 0xb7d9a18a
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: New value of fp=(nil) failed sanity check, terminating stack trace!
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: 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 21:31:15 uk2-host2 mysqld[28311]: stack trace is much more helpful in diagnosing the problem, so please do 
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: resolve it
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: Trying to get some variables.
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: Some pointers may be invalid and cause the dump to abort...
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: thd->query at 0x9d645f8 = 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 21:31:15 uk2-host2 mysqld[28311]: thd->thread_id=578
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: The manual page at http://www.mysql.com/doc/en/Crashing.html contains
daemon.log.3:Oct 10 21:31:15 uk2-host2 mysqld[28311]: information that should help you find out what is causing the crash.