Dec 28 22:51:51 ns26597 mysqld_safe[4204]: started
Dec 28 22:51:51 ns26597 mysqld[4207]: 071228 22:51:51  InnoDB: Database was not shut down normally!
Dec 28 22:51:51 ns26597 mysqld[4207]: InnoDB: Starting crash recovery.
Dec 28 22:51:51 ns26597 mysqld[4207]: InnoDB: Reading tablespace information from the .ibd files...
Dec 28 22:51:51 ns26597 mysqld[4207]: InnoDB: Restoring possible half-written data pages from the doublewrite
Dec 28 22:51:51 ns26597 mysqld[4207]: InnoDB: buffer...
Dec 28 22:51:51 ns26597 mysqld[4207]: 071228 22:51:51  InnoDB: Starting log scan based on checkpoint at
Dec 28 22:51:51 ns26597 mysqld[4207]: InnoDB: log sequence number 4 576510016.
Dec 28 22:51:51 ns26597 mysqld[4207]: InnoDB: Doing recovery: scanned up to log sequence number 4 576510382
Dec 28 22:51:51 ns26597 mysqld[4207]: InnoDB: 1 transaction(s) which must be rolled back or cleaned up
Dec 28 22:51:51 ns26597 mysqld[4207]: InnoDB: in total 28 row operations to undo
Dec 28 22:51:51 ns26597 mysqld[4207]: InnoDB: Trx id counter is 0 6800640
Dec 28 22:51:51 ns26597 mysqld[4207]: 071228 22:51:51  InnoDB: Starting an apply batch of log records to the database...
Dec 28 22:51:51 ns26597 mysqld[4207]: InnoDB: Progress in percents: 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 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
Dec 28 22:51:51 ns26597 mysqld[4207]: InnoDB: Apply batch completed
Dec 28 22:51:51 ns26597 mysqld[4207]: InnoDB: Last MySQL binlog file position 0 104984198, file name /home/log/mysql-bin.1
Dec 28 22:51:51 ns26597 mysqld[4207]: 071228 22:51:51  InnoDB: Started; log sequence number 4 576510382
Dec 28 22:51:51 ns26597 mysqld[4207]: InnoDB: Starting in background the rollback of uncommitted transactions
Dec 28 22:51:51 ns26597 mysqld[4207]: 071228 22:51:51  InnoDB: Rolling back trx with id 0 6800203, 28 rows to undo
Dec 28 22:51:51 ns26597 mysqld[4207]: InnoDB: Error: trying to access page number 3252085469 in space 0,
Dec 28 22:51:51 ns26597 mysqld[4207]: InnoDB: space name ./ibdata1,
Dec 28 22:51:51 ns26597 mysqld[4207]: InnoDB: which is outside the tablespace bounds.
Dec 28 22:51:51 ns26597 mysqld[4207]: InnoDB: Byte offset 0, len 16384, i/o type 10.
Dec 28 22:51:51 ns26597 mysqld[4207]: InnoDB: If you get this error at mysqld startup, please check that
Dec 28 22:51:51 ns26597 mysqld[4207]: InnoDB: your my.cnf matches the ibdata files that you have in the
Dec 28 22:51:51 ns26597 mysqld[4207]: InnoDB: MySQL server.
Dec 28 22:51:51 ns26597 mysqld[4207]: 071228 22:51:51InnoDB: Assertion failure in thread 3016297376 in file fil0fil.c line 3959
Dec 28 22:51:51 ns26597 mysqld[4207]: InnoDB: We intentionally generate a memory trap.
Dec 28 22:51:51 ns26597 mysqld[4207]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
Dec 28 22:51:51 ns26597 mysqld[4207]: InnoDB: If you get repeated assertion failures or crashes, even
Dec 28 22:51:51 ns26597 mysqld[4207]: InnoDB: immediately after the mysqld startup, there may be
Dec 28 22:51:51 ns26597 mysqld[4207]: InnoDB: corruption in the InnoDB tablespace. Please refer to
Dec 28 22:51:51 ns26597 mysqld[4207]: InnoDB: http://dev.mysql.com/doc/mysql/en/Forcing_recovery.html
Dec 28 22:51:51 ns26597 mysqld[4207]: InnoDB: about forcing recovery.
Dec 28 22:51:51 ns26597 mysqld[4207]: mysqld got signal 11;
Dec 28 22:51:51 ns26597 mysqld[4207]: This could be because you hit a bug. It is also possible that this binary
Dec 28 22:51:51 ns26597 mysqld[4207]: or one of the libraries it was linked against is corrupt, improperly built,
Dec 28 22:51:51 ns26597 mysqld[4207]: or misconfigured. This error can also be caused by malfunctioning hardware.
Dec 28 22:51:51 ns26597 mysqld[4207]: We will try our best to scrape up some info that will hopefully help diagnose
Dec 28 22:51:51 ns26597 mysqld[4207]: the problem, but since we have already crashed, something is definitely wrong
Dec 28 22:51:51 ns26597 mysqld[4207]: and this may fail.
Dec 28 22:51:51 ns26597 mysqld[4207]: 
Dec 28 22:51:51 ns26597 mysqld[4207]: key_buffer_size=167772160
Dec 28 22:51:51 ns26597 mysqld[4207]: read_buffer_size=131072
Dec 28 22:51:51 ns26597 mysqld[4207]: max_used_connections=0
Dec 28 22:51:51 ns26597 mysqld[4207]: max_connections=100
Dec 28 22:51:51 ns26597 mysqld[4207]: threads_connected=0
Dec 28 22:51:51 ns26597 mysqld[4207]: It is possible that mysqld could use up to 
Dec 28 22:51:51 ns26597 kernel: grsec: From 81.241.87.195: signal 11 sent to /usr/sbin/mysqld[mysqld:4212] uid/euid:105/105 gid/egid:111/111, parent /usr/bin/mysqld_safe[mysqld_safe:4145] uid/euid:0/0 gid/egid:0/0
Dec 28 22:51:51 ns26597 mysqld[4207]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 381439 K
Dec 28 22:51:51 ns26597 mysqld[4207]: bytes of memory
Dec 28 22:51:51 ns26597 mysqld[4207]: Hope that's ok; if not, decrease some variables in the equation.
Dec 28 22:51:51 ns26597 mysqld[4207]: 
Dec 28 22:51:51 ns26597 mysqld[4207]: thd=(nil)
Dec 28 22:51:51 ns26597 mysqld[4207]: Attempting backtrace. You can use the following information to find out
Dec 28 22:51:51 ns26597 mysqld[4207]: where mysqld died. If you see no messages after this, something went
Dec 28 22:51:51 ns26597 mysqld[4207]: terribly wrong...
Dec 28 22:51:51 ns26597 mysqld[4207]: Cannot determine thread, fp=0xb3c8f998, backtrace may not be correct.
Dec 28 22:51:51 ns26597 mysqld[4207]: Stack range sanity check OK, backtrace follows:
Dec 28 22:51:51 ns26597 mysqld[4207]: 0x81bb263
Dec 28 22:51:51 ns26597 mysqld[4207]: 0xffffe420
Dec 28 22:51:51 ns26597 mysqld[4207]: 0x8380124
Dec 28 22:51:51 ns26597 mysqld[4207]: 0x8380124
Dec 28 22:51:51 ns26597 mysqld[4207]: 0x8375bd3
Dec 28 22:51:51 ns26597 mysqld[4207]: 0x839ac27
Dec 28 22:51:51 ns26597 mysqld[4207]: 0x839b1a8
Dec 28 22:51:51 ns26597 mysqld[4207]: 0x835af1f
Dec 28 22:51:51 ns26597 mysqld[4207]: 0x836cfe4
Dec 28 22:51:51 ns26597 mysqld[4207]: 0x836bdf7
Dec 28 22:51:51 ns26597 mysqld[4207]: Stack trace seems successful - bottom reached
Dec 28 22:51:51 ns26597 mysqld[4207]: Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved
Dec 28 22:51:51 ns26597 mysqld[4207]: stack trace is much more helpful in diagnosing the problem, so please do 
Dec 28 22:51:51 ns26597 mysqld[4207]: resolve it
Dec 28 22:51:51 ns26597 mysqld[4207]: The manual page at http://www.mysql.com/doc/en/Crashing.html contains
Dec 28 22:51:51 ns26597 mysqld[4207]: information that should help you find out what is causing the crash.
Dec 28 22:51:51 ns26597 mysqld_safe[4217]: ended
Dec 28 22:52:05 ns26597 /etc/init.d/mysql[4352]: 0 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in
Dec 28 22:52:05 ns26597 /etc/init.d/mysql[4352]: ^G/usr/bin/mysqladmin: connect to server at 'localhost' failed
Dec 28 22:52:05 ns26597 /etc/init.d/mysql[4352]: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)'
Dec 28 22:52:05 ns26597 /etc/init.d/mysql[4352]: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!
Dec 28 22:52:05 ns26597 /etc/init.d/mysql[4352]: 
Dec 28 22:52:56 ns26597 sm-mta[3911]: lBOEEXBl028