daemon.log:Nov 17 13:30:01 uk2-host2 mysqld[11744]: mysqld got signal 11;
daemon.log:Nov 17 13:30:01 uk2-host2 mysqld[11744]: This could be because you hit a bug. It is also possible that this binary
daemon.log:Nov 17 13:30:01 uk2-host2 mysqld[11744]: or one of the libraries it was linked against is corrupt, improperly built,
daemon.log:Nov 17 13:30:01 uk2-host2 mysqld[11744]: or misconfigured. This error can also be caused by malfunctioning hardware.
daemon.log:Nov 17 13:30:01 uk2-host2 mysqld[11744]: We will try our best to scrape up some info that will hopefully help diagnose
daemon.log:Nov 17 13:30:01 uk2-host2 mysqld[11744]: the problem, but since we have already crashed, something is definitely wrong
daemon.log:Nov 17 13:30:01 uk2-host2 mysqld[11744]: and this may fail.
daemon.log:Nov 17 13:30:01 uk2-host2 mysqld[11744]: 
daemon.log:Nov 17 13:30:01 uk2-host2 mysqld[11744]: key_buffer_size=16777216
daemon.log:Nov 17 13:30:01 uk2-host2 mysqld[11744]: read_buffer_size=2093056
daemon.log:Nov 17 13:30:01 uk2-host2 mysqld[11744]: max_used_connections=47
daemon.log:Nov 17 13:30:01 uk2-host2 mysqld[11744]: max_connections=100
daemon.log:Nov 17 13:30:01 uk2-host2 mysqld[11744]: threads_connected=32
daemon.log:Nov 17 13:30:01 uk2-host2 mysqld[11744]: It is possible that mysqld could use up to 
daemon.log:Nov 17 13:30:01 uk2-host2 mysqld[11744]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1039983 K
daemon.log:Nov 17 13:30:01 uk2-host2 mysqld[11744]: bytes of memory
daemon.log:Nov 17 13:30:01 uk2-host2 mysqld[11744]: Hope that's ok; if not, decrease some variables in the equation.
daemon.log:Nov 17 13:30:01 uk2-host2 mysqld[11744]: 
daemon.log:Nov 17 13:30:01 uk2-host2 mysqld[11744]: thd=0x9dba260
daemon.log:Nov 17 13:30:01 uk2-host2 mysqld[11744]: Attempting backtrace. You can use the following information to find out
daemon.log:Nov 17 13:30:01 uk2-host2 mysqld[11744]: where mysqld died. If you see no messages after this, something went
daemon.log:Nov 17 13:30:01 uk2-host2 mysqld[11744]: terribly wrong...
daemon.log:Nov 17 13:30:01 uk2-host2 mysqld[11744]: Cannot determine thread, fp=0x24144d78, backtrace may not be correct.
daemon.log:Nov 17 13:30:01 uk2-host2 mysqld[11744]: Stack range sanity check OK, backtrace follows:
daemon.log:Nov 17 13:30:01 uk2-host2 mysqld[11744]: 0x81ba944
daemon.log:Nov 17 13:30:01 uk2-host2 mysqld[11744]: 0xffffe420
daemon.log:Nov 17 13:30:01 uk2-host2 mysqld[11744]: 0xa1440e4
daemon.log:Nov 17 13:30:01 uk2-host2 mysqld[11744]: 0x81d35a8
daemon.log:Nov 17 13:30:01 uk2-host2 mysqld[11744]: 0x8227620
daemon.log:Nov 17 13:30:01 uk2-host2 mysqld[11744]: 0x82263ea
daemon.log:Nov 17 13:30:01 uk2-host2 mysqld[11744]: 0x81ce7fd
daemon.log:Nov 17 13:30:01 uk2-host2 mysqld[11744]: 0x81cd37d
daemon.log:Nov 17 13:30:01 uk2-host2 mysqld[11744]: 0x81cc812
daemon.log:Nov 17 13:30:01 uk2-host2 mysqld[11744]: 0xb7f89b63
daemon.log:Nov 17 13:30:01 uk2-host2 mysqld[11744]: 0xb7e0118a
daemon.log:Nov 17 13:30:01 uk2-host2 mysqld[11744]: New value of fp=(nil) failed sanity check, terminating stack trace!
daemon.log:Nov 17 13:30:01 uk2-host2 mysqld[11744]: 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:Nov 17 13:30:01 uk2-host2 mysqld[11744]: stack trace is much more helpful in diagnosing the problem, so please do 
daemon.log:Nov 17 13:30:01 uk2-host2 mysqld[11744]: resolve it
daemon.log:Nov 17 13:30:01 uk2-host2 mysqld[11744]: Trying to get some variables.
daemon.log:Nov 17 13:30:01 uk2-host2 mysqld[11744]: Some pointers may be invalid and cause the dump to abort...
daemon.log:Nov 17 13:30:01 uk2-host2 mysqld[11744]: thd->query at 0x9e03518 = DELETE FROM share_network  USING share_network,        (friends AS f         RIGHT JOIN share_network AS s         ON f.owner_username=s.username AND            f.username=s.shares_with)  WHERE share_network.username=s.username AND        share_network.shares_with=s.shares_with AND        f.owner_username IS NULL
daemon.log:Nov 17 13:30:01 uk2-host2 mysqld[11744]: thd->thread_id=367
daemon.log:Nov 17 13:30:01 uk2-host2 mysqld[11744]: The manual page at http://www.mysql.com/doc/en/Crashing.html contains
daemon.log:Nov 17 13:30:01 uk2-host2 mysqld[11744]: information that should help you find out what is causing the crash.
daemon.log.0:Nov  2 15:08:43 uk2-host2 mysqld[11744]: 061102 15:08:43  InnoDB: Database was not shut down normally!
daemon.log.0:Nov  2 15:08:43 uk2-host2 mysqld[11744]: InnoDB: Starting crash recovery.
daemon.log.0:Nov  2 15:08:43 uk2-host2 mysqld[11744]: InnoDB: Reading tablespace information from the .ibd files...
daemon.log.0:Nov  2 15:08:43 uk2-host2 mysqld[11744]: InnoDB: Restoring possible half-written data pages from the doublewrite
daemon.log.0:Nov  2 15:08:43 uk2-host2 mysqld[11744]: InnoDB: buffer...
daemon.log.0:Nov  2 15:08:43 uk2-host2 mysqld[11744]: 061102 15:08:43  InnoDB: Starting log scan based on checkpoint at
daemon.log.0:Nov  2 15:08:43 uk2-host2 mysqld[11744]: InnoDB: log sequence number 0 34765989.
daemon.log.0:Nov  2 15:08:43 uk2-host2 mysqld[11744]: InnoDB: Doing recovery: scanned up to log sequence number 0 34766651
daemon.log.0:Nov  2 15:08:43 uk2-host2 mysqld[11744]: 061102 15:08:43  InnoDB: Starting an apply batch of log records to the database...
daemon.log.0:Nov  2 15:08:44 uk2-host2 mysqld[11744]: InnoDB: Progress in percents: 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.0:Nov  2 15:08:44 uk2-host2 mysqld[11744]: InnoDB: Apply batch completed
daemon.log.0:Nov  2 15:08:44 uk2-host2 mysqld[11744]: InnoDB: Last MySQL binlog file position 0 377524, file name ./mysql-bin.000017
daemon.log.0:Nov  2 15:08:44 uk2-host2 mysqld[11744]: 061102 15:08:44  InnoDB: Started; log sequence number 0 34766651
daemon.log.0:Nov  2 15:08:44 uk2-host2 mysqld[11744]: 061102 15:08:44 [Note] Recovering after a crash using mysql-bin
daemon.log.0:Nov  2 15:08:44 uk2-host2 mysqld[11744]: 061102 15:08:44 [Note] Starting crash recovery...
daemon.log.0:Nov  2 15:08:44 uk2-host2 mysqld[11744]: 061102 15:08:44 [Note] Crash recovery finished.
daemon.log.0:Nov  2 15:08:46 uk2-host2 mysqld[11744]: 061102 15:08:46 [Note] /usr/sbin/mysqld: ready for connections.
daemon.log.0:Nov  2 15:08:46 uk2-host2 mysqld[11744]: Version: '5.0.24a-Debian_2.dotdeb.0-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  Dotdeb Sarge backport