110502 22:00:01 [ERROR] /usr/local/mysql51/libexec/mysqld: Deadlock found when trying to get lock; try restarting transaction
110502 22:00:01 [ERROR] /usr/local/mysql51/libexec/mysqld: Sort aborted
110503 19:25:09 [Note] /usr/local/mysql51/libexec/mysqld: Normal shutdown

110503 19:25:09 [Note] Event Scheduler: Purging the queue. 0 events
110503 19:25:09  InnoDB: Starting shutdown...
110503 19:28:47  InnoDB: Shutdown completed; log sequence number 8174450611678
110503 19:28:47 [Note] /usr/local/mysql51/libexec/mysqld: Shutdown complete

110503 19:28:47 mysqld_safe mysqld from pid file /data/mysql/minerdb01.pid ended
110503 19:37:31 mysqld_safe Starting mysqld daemon with databases from /data/mysql
InnoDB: Warning: innodb_overwrite_relay_log_info is enabled. Updates in other storage engines may have problem with consistency.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3
110503 19:37:32  InnoDB: highest supported file format is Barracuda.
110503 19:37:33 Percona XtraDB (http://www.percona.com) 1.0.8-11.2 started; log sequence number 8298149359628
InnoDB: something wrong with relay-info.log. InnoDB will not overwrite it.
110503 19:37:34 [Note] Event Scheduler: Loaded 0 events
110503 19:37:34 [Note] /usr/local/mysql51/libexec/mysqld: ready for connections.
Version: '5.1.47-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
110503 19:37:44  InnoDB: Error: page 4 log sequence number 8299215792744
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:37:44  InnoDB: Error: page 1 log sequence number 8299215891574
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:37:44  InnoDB: Error: page 20 log sequence number 8299215528487
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:37:44  InnoDB: Error: page 106216 log sequence number 8299348330353
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:37:44  InnoDB: Error: page 98305 log sequence number 8299434590706
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:37:44  InnoDB: Error: page 5 log sequence number 8299215789101
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:37:44  InnoDB: Error: page 114689 log sequence number 8299405235524
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:37:44  InnoDB: Error: page 6 log sequence number 8299215192961
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:37:44  InnoDB: Error: page 41756 log sequence number 8299307763762
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:37:44  InnoDB: Error: page 40961 log sequence number 8299348114573
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:37:44  InnoDB: Error: page 3 log sequence number 8299215891509
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Error: trying to access page number 1768711273 in space 995,
InnoDB: space name ./newsminer/pendingrobots.ibd,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 8192, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
110503 19:37:44  InnoDB: Assertion failure in thread 140634645006096 in file fil/fil0fil.c line 4686
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
110503 19:37:44 - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=33554432
read_buffer_size=2097152
max_used_connections=1
max_threads=500
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2086162 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = (nil) thread_stack 0x30000
/usr/local/mysql51/libexec/mysqld(my_print_stacktrace+0x29) [0x887c49]
/usr/local/mysql51/libexec/mysqld(handle_segfault+0x40d) [0x5abacd]
/lib/libpthread.so.0(+0xf8f0) [0x7feccee588f0]
/lib/libc.so.6(gsignal+0x35) [0x7feccdcf4a75]
/lib/libc.so.6(abort+0x180) [0x7feccdcf85c0]
/usr/local/mysql51/libexec/mysqld() [0x813ddf]
/usr/local/mysql51/libexec/mysqld() [0x7f2aaf]
/usr/local/mysql51/libexec/mysqld() [0x7f2fd4]
/usr/local/mysql51/libexec/mysqld() [0x7eb11c]
/usr/local/mysql51/libexec/mysqld() [0x7d6b5b]
/usr/local/mysql51/libexec/mysqld() [0x795327]
/usr/local/mysql51/libexec/mysqld() [0x7939f3]
/usr/local/mysql51/libexec/mysqld() [0x794443]
/usr/local/mysql51/libexec/mysqld() [0x794da4]
/usr/local/mysql51/libexec/mysqld() [0x77fc6d]
/usr/local/mysql51/libexec/mysqld() [0x7af1ae]
/usr/local/mysql51/libexec/mysqld() [0x7a5bab]
/lib/libpthread.so.0(+0x69ca) [0x7feccee4f9ca]
/lib/libc.so.6(clone+0x6d) [0x7feccdda76fd]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
110503 19:37:44 mysqld_safe Number of processes running now: 0
110503 19:37:44 mysqld_safe mysqld restarted
InnoDB: Warning: innodb_overwrite_relay_log_info is enabled. Updates in other storage engines may have problem with consistency.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3
110503 19:37:45  InnoDB: highest supported file format is Barracuda.
110503 19:37:46 Percona XtraDB (http://www.percona.com) 1.0.8-11.2 started; log sequence number 8298149359628
InnoDB: something wrong with relay-info.log. InnoDB will not overwrite it.
110503 19:37:46 [Note] Recovering after a crash using mysql-bin
110503 19:37:46 [Note] Starting crash recovery...
110503 19:37:46 [Note] Crash recovery finished.
110503 19:37:46 [Note] Event Scheduler: Loaded 0 events
110503 19:37:46 [Note] /usr/local/mysql51/libexec/mysqld: ready for connections.
Version: '5.1.47-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
110503 19:37:56  InnoDB: Error: page 4 log sequence number 8299215792744
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:37:56  InnoDB: Error: page 1 log sequence number 8299215891574
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:37:56  InnoDB: Error: page 20 log sequence number 8299215528487
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:37:56  InnoDB: Error: page 106216 log sequence number 8299348330353
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:37:56  InnoDB: Error: page 98305 log sequence number 8299434590706
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:37:56  InnoDB: Error: page 5 log sequence number 8299215789101
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:37:56  InnoDB: Error: page 114689 log sequence number 8299405235524
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:37:56  InnoDB: Error: page 6 log sequence number 8299215192961
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:37:56  InnoDB: Error: page 41756 log sequence number 8299307763762
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:37:56  InnoDB: Error: page 40961 log sequence number 8299348114573
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:37:56  InnoDB: Error: page 3 log sequence number 8299215891509
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Error: trying to access page number 1768711273 in space 995,
InnoDB: space name ./newsminer/pendingrobots.ibd,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 8192, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
110503 19:37:56  InnoDB: Assertion failure in thread 140124223203088 in file fil/fil0fil.c line 4686
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
110503 19:37:56 - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=33554432
read_buffer_size=2097152
max_used_connections=1
max_threads=500
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2086162 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = (nil) thread_stack 0x30000
/usr/local/mysql51/libexec/mysqld(my_print_stacktrace+0x29) [0x887c49]
/usr/local/mysql51/libexec/mysqld(handle_segfault+0x40d) [0x5abacd]
/lib/libpthread.so.0(+0xf8f0) [0x7f75f762e8f0]
/lib/libc.so.6(gsignal+0x35) [0x7f75f64caa75]
/lib/libc.so.6(abort+0x180) [0x7f75f64ce5c0]
/usr/local/mysql51/libexec/mysqld() [0x813ddf]
/usr/local/mysql51/libexec/mysqld() [0x7f2aaf]
/usr/local/mysql51/libexec/mysqld() [0x7f2fd4]
/usr/local/mysql51/libexec/mysqld() [0x7eb11c]
/usr/local/mysql51/libexec/mysqld() [0x7d6b5b]
/usr/local/mysql51/libexec/mysqld() [0x795327]
/usr/local/mysql51/libexec/mysqld() [0x7939f3]
/usr/local/mysql51/libexec/mysqld() [0x794443]
/usr/local/mysql51/libexec/mysqld() [0x794da4]
/usr/local/mysql51/libexec/mysqld() [0x77fc6d]
/usr/local/mysql51/libexec/mysqld() [0x7af1ae]
/usr/local/mysql51/libexec/mysqld() [0x7a5bab]
/lib/libpthread.so.0(+0x69ca) [0x7f75f76259ca]
/lib/libc.so.6(clone+0x6d) [0x7f75f657d6fd]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
110503 19:37:56 mysqld_safe Number of processes running now: 0
110503 19:37:56 mysqld_safe mysqld restarted
InnoDB: Warning: innodb_overwrite_relay_log_info is enabled. Updates in other storage engines may have problem with consistency.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3
110503 19:37:57  InnoDB: highest supported file format is Barracuda.
110503 19:37:58 Percona XtraDB (http://www.percona.com) 1.0.8-11.2 started; log sequence number 8298149359628
InnoDB: something wrong with relay-info.log. InnoDB will not overwrite it.
110503 19:37:58 [Note] Recovering after a crash using mysql-bin
110503 19:37:58 [Note] Starting crash recovery...
110503 19:37:58 [Note] Crash recovery finished.
110503 19:37:58 [Note] Event Scheduler: Loaded 0 events
110503 19:37:58 [Note] /usr/local/mysql51/libexec/mysqld: ready for connections.
Version: '5.1.47-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
110503 19:38:08  InnoDB: Error: page 4 log sequence number 8299215792744
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:08  InnoDB: Error: page 1 log sequence number 8299215891574
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:08  InnoDB: Error: page 20 log sequence number 8299215528487
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:09  InnoDB: Error: page 106216 log sequence number 8299348330353
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:09  InnoDB: Error: page 98305 log sequence number 8299434590706
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:09  InnoDB: Error: page 5 log sequence number 8299215789101
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:09  InnoDB: Error: page 114689 log sequence number 8299405235524
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:09  InnoDB: Error: page 6 log sequence number 8299215192961
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:09  InnoDB: Error: page 41756 log sequence number 8299307763762
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:09  InnoDB: Error: page 40961 log sequence number 8299348114573
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:09  InnoDB: Error: page 3 log sequence number 8299215891509
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Error: trying to access page number 1768711273 in space 995,
InnoDB: space name ./newsminer/pendingrobots.ibd,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 8192, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
110503 19:38:09  InnoDB: Assertion failure in thread 139914184091408 in file fil/fil0fil.c line 4686
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
110503 19:38:09 - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=33554432
read_buffer_size=2097152
max_used_connections=1
max_threads=500
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2086162 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = (nil) thread_stack 0x30000
/usr/local/mysql51/libexec/mysqld(my_print_stacktrace+0x29) [0x887c49]
/usr/local/mysql51/libexec/mysqld(handle_segfault+0x40d) [0x5abacd]
/lib/libpthread.so.0(+0xf8f0) [0x7f45101468f0]
/lib/libc.so.6(gsignal+0x35) [0x7f450efe2a75]
/lib/libc.so.6(abort+0x180) [0x7f450efe65c0]
/usr/local/mysql51/libexec/mysqld() [0x813ddf]
/usr/local/mysql51/libexec/mysqld() [0x7f2aaf]
/usr/local/mysql51/libexec/mysqld() [0x7f2fd4]
/usr/local/mysql51/libexec/mysqld() [0x7eb11c]
/usr/local/mysql51/libexec/mysqld() [0x7d6b5b]
/usr/local/mysql51/libexec/mysqld() [0x795327]
/usr/local/mysql51/libexec/mysqld() [0x7939f3]
/usr/local/mysql51/libexec/mysqld() [0x794443]
/usr/local/mysql51/libexec/mysqld() [0x794da4]
/usr/local/mysql51/libexec/mysqld() [0x77fc6d]
/usr/local/mysql51/libexec/mysqld() [0x7af1ae]
/usr/local/mysql51/libexec/mysqld() [0x7a5bab]
/lib/libpthread.so.0(+0x69ca) [0x7f451013d9ca]
/lib/libc.so.6(clone+0x6d) [0x7f450f0956fd]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
110503 19:38:09 mysqld_safe Number of processes running now: 0
110503 19:38:09 mysqld_safe mysqld restarted
InnoDB: Warning: innodb_overwrite_relay_log_info is enabled. Updates in other storage engines may have problem with consistency.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3
110503 19:38:10  InnoDB: highest supported file format is Barracuda.
110503 19:38:11 Percona XtraDB (http://www.percona.com) 1.0.8-11.2 started; log sequence number 8298149359628
InnoDB: something wrong with relay-info.log. InnoDB will not overwrite it.
110503 19:38:11 [Note] Recovering after a crash using mysql-bin
110503 19:38:11 [Note] Starting crash recovery...
110503 19:38:11 [Note] Crash recovery finished.
110503 19:38:11 [Note] Event Scheduler: Loaded 0 events
110503 19:38:11 [Note] /usr/local/mysql51/libexec/mysqld: ready for connections.
Version: '5.1.47-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
110503 19:38:21  InnoDB: Error: page 4 log sequence number 8299215792744
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:21  InnoDB: Error: page 1 log sequence number 8299215891574
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:21  InnoDB: Error: page 20 log sequence number 8299215528487
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:21  InnoDB: Error: page 106216 log sequence number 8299348330353
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:21  InnoDB: Error: page 98305 log sequence number 8299434590706
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:21  InnoDB: Error: page 5 log sequence number 8299215789101
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:21  InnoDB: Error: page 114689 log sequence number 8299405235524
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:21  InnoDB: Error: page 6 log sequence number 8299215192961
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:21  InnoDB: Error: page 41756 log sequence number 8299307763762
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:21  InnoDB: Error: page 40961 log sequence number 8299348114573
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:21  InnoDB: Error: page 3 log sequence number 8299215891509
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Error: trying to access page number 1768711273 in space 995,
InnoDB: space name ./newsminer/pendingrobots.ibd,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 8192, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
110503 19:38:21  InnoDB: Assertion failure in thread 139997456717584 in file fil/fil0fil.c line 4686
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
110503 19:38:21 - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=33554432
read_buffer_size=2097152
max_used_connections=1
max_threads=500
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2086162 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = (nil) thread_stack 0x30000
/usr/local/mysql51/libexec/mysqld(my_print_stacktrace+0x29) [0x887c49]
/usr/local/mysql51/libexec/mysqld(handle_segfault+0x40d) [0x5abacd]
/lib/libpthread.so.0(+0xf8f0) [0x7f587383d8f0]
/lib/libc.so.6(gsignal+0x35) [0x7f58726d9a75]
/lib/libc.so.6(abort+0x180) [0x7f58726dd5c0]
/usr/local/mysql51/libexec/mysqld() [0x813ddf]
/usr/local/mysql51/libexec/mysqld() [0x7f2aaf]
/usr/local/mysql51/libexec/mysqld() [0x7f2fd4]
/usr/local/mysql51/libexec/mysqld() [0x7eb11c]
/usr/local/mysql51/libexec/mysqld() [0x7d6b5b]
/usr/local/mysql51/libexec/mysqld() [0x795327]
/usr/local/mysql51/libexec/mysqld() [0x7939f3]
/usr/local/mysql51/libexec/mysqld() [0x794443]
/usr/local/mysql51/libexec/mysqld() [0x794da4]
/usr/local/mysql51/libexec/mysqld() [0x77fc6d]
/usr/local/mysql51/libexec/mysqld() [0x7af1ae]
/usr/local/mysql51/libexec/mysqld() [0x7a5bab]
/lib/libpthread.so.0(+0x69ca) [0x7f58738349ca]
/lib/libc.so.6(clone+0x6d) [0x7f587278c6fd]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
110503 19:38:21 mysqld_safe Number of processes running now: 0
110503 19:38:21 mysqld_safe mysqld restarted
InnoDB: Warning: innodb_overwrite_relay_log_info is enabled. Updates in other storage engines may have problem with consistency.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3
110503 19:38:22  InnoDB: highest supported file format is Barracuda.
110503 19:38:23 Percona XtraDB (http://www.percona.com) 1.0.8-11.2 started; log sequence number 8298149359628
InnoDB: something wrong with relay-info.log. InnoDB will not overwrite it.
110503 19:38:23 [Note] Recovering after a crash using mysql-bin
110503 19:38:23 [Note] Starting crash recovery...
110503 19:38:23 [Note] Crash recovery finished.
110503 19:38:23 [Note] Event Scheduler: Loaded 0 events
110503 19:38:23 [Note] /usr/local/mysql51/libexec/mysqld: ready for connections.
Version: '5.1.47-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
110503 19:38:33  InnoDB: Error: page 4 log sequence number 8299215792744
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:33  InnoDB: Error: page 1 log sequence number 8299215891574
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:33  InnoDB: Error: page 20 log sequence number 8299215528487
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:33  InnoDB: Error: page 106216 log sequence number 8299348330353
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:33  InnoDB: Error: page 98305 log sequence number 8299434590706
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:33  InnoDB: Error: page 5 log sequence number 8299215789101
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:33  InnoDB: Error: page 114689 log sequence number 8299405235524
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:33  InnoDB: Error: page 6 log sequence number 8299215192961
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:33  InnoDB: Error: page 41756 log sequence number 8299307763762
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:33  InnoDB: Error: page 40961 log sequence number 8299348114573
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:33  InnoDB: Error: page 3 log sequence number 8299215891509
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Error: trying to access page number 1768711273 in space 995,
InnoDB: space name ./newsminer/pendingrobots.ibd,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 8192, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
110503 19:38:33  InnoDB: Assertion failure in thread 139876226701072 in file fil/fil0fil.c line 4686
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
110503 19:38:33 - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=33554432
read_buffer_size=2097152
max_used_connections=1
max_threads=500
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2086162 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = (nil) thread_stack 0x30000
/usr/local/mysql51/libexec/mysqld(my_print_stacktrace+0x29) [0x887c49]
/usr/local/mysql51/libexec/mysqld(handle_segfault+0x40d) [0x5abacd]
/lib/libpthread.so.0(+0xf8f0) [0x7f3c39a498f0]
/lib/libc.so.6(gsignal+0x35) [0x7f3c388e5a75]
/lib/libc.so.6(abort+0x180) [0x7f3c388e95c0]
/usr/local/mysql51/libexec/mysqld() [0x813ddf]
/usr/local/mysql51/libexec/mysqld() [0x7f2aaf]
/usr/local/mysql51/libexec/mysqld() [0x7f2fd4]
/usr/local/mysql51/libexec/mysqld() [0x7eb11c]
/usr/local/mysql51/libexec/mysqld() [0x7d6b5b]
/usr/local/mysql51/libexec/mysqld() [0x795327]
/usr/local/mysql51/libexec/mysqld() [0x7939f3]
/usr/local/mysql51/libexec/mysqld() [0x794443]
/usr/local/mysql51/libexec/mysqld() [0x794da4]
/usr/local/mysql51/libexec/mysqld() [0x77fc6d]
/usr/local/mysql51/libexec/mysqld() [0x7af1ae]
/usr/local/mysql51/libexec/mysqld() [0x7a5bab]
/lib/libpthread.so.0(+0x69ca) [0x7f3c39a409ca]
/lib/libc.so.6(clone+0x6d) [0x7f3c389986fd]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
110503 19:38:34 mysqld_safe Number of processes running now: 0
110503 19:38:34 mysqld_safe mysqld restarted
InnoDB: Warning: innodb_overwrite_relay_log_info is enabled. Updates in other storage engines may have problem with consistency.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3
110503 19:38:35  InnoDB: highest supported file format is Barracuda.
110503 19:38:36 Percona XtraDB (http://www.percona.com) 1.0.8-11.2 started; log sequence number 8298149359628
InnoDB: something wrong with relay-info.log. InnoDB will not overwrite it.
110503 19:38:36 [Note] Recovering after a crash using mysql-bin
110503 19:38:36 [Note] Starting crash recovery...
110503 19:38:36 [Note] Crash recovery finished.
110503 19:38:36 [Note] Event Scheduler: Loaded 0 events
110503 19:38:36 [Note] /usr/local/mysql51/libexec/mysqld: ready for connections.
Version: '5.1.47-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
110503 19:38:46  InnoDB: Error: page 4 log sequence number 8299215792744
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:46  InnoDB: Error: page 1 log sequence number 8299215891574
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:46  InnoDB: Error: page 20 log sequence number 8299215528487
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:46  InnoDB: Error: page 106216 log sequence number 8299348330353
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:46  InnoDB: Error: page 98305 log sequence number 8299434590706
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:46  InnoDB: Error: page 5 log sequence number 8299215789101
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:46  InnoDB: Error: page 114689 log sequence number 8299405235524
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:46  InnoDB: Error: page 6 log sequence number 8299215192961
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:46  InnoDB: Error: page 41756 log sequence number 8299307763762
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:46  InnoDB: Error: page 40961 log sequence number 8299348114573
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:46  InnoDB: Error: page 3 log sequence number 8299215891509
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Error: trying to access page number 1768711273 in space 995,
InnoDB: space name ./newsminer/pendingrobots.ibd,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 8192, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
110503 19:38:46  InnoDB: Assertion failure in thread 140595562297104 in file fil/fil0fil.c line 4686
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
110503 19:38:46 - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=33554432
read_buffer_size=2097152
max_used_connections=1
max_threads=500
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2086162 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = (nil) thread_stack 0x30000
/usr/local/mysql51/libexec/mysqld(my_print_stacktrace+0x29) [0x887c49]
/usr/local/mysql51/libexec/mysqld(handle_segfault+0x40d) [0x5abacd]
/lib/libpthread.so.0(+0xf8f0) [0x7fe3b562b8f0]
/lib/libc.so.6(gsignal+0x35) [0x7fe3b44c7a75]
/lib/libc.so.6(abort+0x180) [0x7fe3b44cb5c0]
/usr/local/mysql51/libexec/mysqld() [0x813ddf]
/usr/local/mysql51/libexec/mysqld() [0x7f2aaf]
/usr/local/mysql51/libexec/mysqld() [0x7f2fd4]
/usr/local/mysql51/libexec/mysqld() [0x7eb11c]
/usr/local/mysql51/libexec/mysqld() [0x7d6b5b]
/usr/local/mysql51/libexec/mysqld() [0x795327]
/usr/local/mysql51/libexec/mysqld() [0x7939f3]
/usr/local/mysql51/libexec/mysqld() [0x794443]
/usr/local/mysql51/libexec/mysqld() [0x794da4]
/usr/local/mysql51/libexec/mysqld() [0x77fc6d]
/usr/local/mysql51/libexec/mysqld() [0x7af1ae]
/usr/local/mysql51/libexec/mysqld() [0x7a5bab]
/lib/libpthread.so.0(+0x69ca) [0x7fe3b56229ca]
/lib/libc.so.6(clone+0x6d) [0x7fe3b457a6fd]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
110503 19:38:46 mysqld_safe Number of processes running now: 0
110503 19:38:46 mysqld_safe mysqld restarted
InnoDB: Warning: innodb_overwrite_relay_log_info is enabled. Updates in other storage engines may have problem with consistency.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3
110503 19:38:47  InnoDB: highest supported file format is Barracuda.
110503 19:38:48 Percona XtraDB (http://www.percona.com) 1.0.8-11.2 started; log sequence number 8298149359628
InnoDB: something wrong with relay-info.log. InnoDB will not overwrite it.
110503 19:38:48 [Note] Recovering after a crash using mysql-bin
110503 19:38:48 [Note] Starting crash recovery...
110503 19:38:48 [Note] Crash recovery finished.
110503 19:38:48 [Note] Event Scheduler: Loaded 0 events
110503 19:38:48 [Note] /usr/local/mysql51/libexec/mysqld: ready for connections.
Version: '5.1.47-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
110503 19:38:58  InnoDB: Error: page 4 log sequence number 8299215792744
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:58  InnoDB: Error: page 1 log sequence number 8299215891574
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:58  InnoDB: Error: page 20 log sequence number 8299215528487
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:58  InnoDB: Error: page 106216 log sequence number 8299348330353
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:58  InnoDB: Error: page 98305 log sequence number 8299434590706
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:58  InnoDB: Error: page 5 log sequence number 8299215789101
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:58  InnoDB: Error: page 114689 log sequence number 8299405235524
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:58  InnoDB: Error: page 6 log sequence number 8299215192961
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:58  InnoDB: Error: page 41756 log sequence number 8299307763762
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:58  InnoDB: Error: page 40961 log sequence number 8299348114573
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:38:58  InnoDB: Error: page 3 log sequence number 8299215891509
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Error: trying to access page number 1768711273 in space 995,
InnoDB: space name ./newsminer/pendingrobots.ibd,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 8192, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
110503 19:38:58  InnoDB: Assertion failure in thread 140070530070288 in file fil/fil0fil.c line 4686
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
110503 19:38:58 - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=33554432
read_buffer_size=2097152
max_used_connections=2
max_threads=500
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2086162 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = (nil) thread_stack 0x30000
/usr/local/mysql51/libexec/mysqld(my_print_stacktrace+0x29) [0x887c49]
/usr/local/mysql51/libexec/mysqld(handle_segfault+0x40d) [0x5abacd]
/lib/libpthread.so.0(+0xf8f0) [0x7f697706b8f0]
/lib/libc.so.6(gsignal+0x35) [0x7f6975f07a75]
/lib/libc.so.6(abort+0x180) [0x7f6975f0b5c0]
/usr/local/mysql51/libexec/mysqld() [0x813ddf]
/usr/local/mysql51/libexec/mysqld() [0x7f2aaf]
/usr/local/mysql51/libexec/mysqld() [0x7f2fd4]
/usr/local/mysql51/libexec/mysqld() [0x7eb11c]
/usr/local/mysql51/libexec/mysqld() [0x7d6b5b]
/usr/local/mysql51/libexec/mysqld() [0x795327]
/usr/local/mysql51/libexec/mysqld() [0x7939f3]
/usr/local/mysql51/libexec/mysqld() [0x794443]
/usr/local/mysql51/libexec/mysqld() [0x794da4]
/usr/local/mysql51/libexec/mysqld() [0x77fc6d]
/usr/local/mysql51/libexec/mysqld() [0x7af1ae]
/usr/local/mysql51/libexec/mysqld() [0x7a5bab]
/lib/libpthread.so.0(+0x69ca) [0x7f69770629ca]
/lib/libc.so.6(clone+0x6d) [0x7f6975fba6fd]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
110503 19:38:58 mysqld_safe Number of processes running now: 0
110503 19:38:58 mysqld_safe mysqld restarted
InnoDB: Warning: innodb_overwrite_relay_log_info is enabled. Updates in other storage engines may have problem with consistency.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3
110503 19:39:00  InnoDB: highest supported file format is Barracuda.
110503 19:39:01 Percona XtraDB (http://www.percona.com) 1.0.8-11.2 started; log sequence number 8298149359628
InnoDB: something wrong with relay-info.log. InnoDB will not overwrite it.
110503 19:39:01 [Note] Recovering after a crash using mysql-bin
110503 19:39:01 [Note] Starting crash recovery...
110503 19:39:01 [Note] Crash recovery finished.
110503 19:39:01 [Note] Event Scheduler: Loaded 0 events
110503 19:39:01 [Note] /usr/local/mysql51/libexec/mysqld: ready for connections.
Version: '5.1.47-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
110503 19:39:11  InnoDB: Error: page 4 log sequence number 8299215792744
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:39:11  InnoDB: Error: page 1 log sequence number 8299215891574
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:39:11  InnoDB: Error: page 20 log sequence number 8299215528487
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:39:11  InnoDB: Error: page 106216 log sequence number 8299348330353
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:39:11  InnoDB: Error: page 98305 log sequence number 8299434590706
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:39:11  InnoDB: Error: page 5 log sequence number 8299215789101
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:39:11  InnoDB: Error: page 114689 log sequence number 8299405235524
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:39:11  InnoDB: Error: page 6 log sequence number 8299215192961
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:39:11  InnoDB: Error: page 41756 log sequence number 8299307763762
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:39:11  InnoDB: Error: page 40961 log sequence number 8299348114573
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:39:11  InnoDB: Error: page 3 log sequence number 8299215891509
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Error: trying to access page number 1768711273 in space 995,
InnoDB: space name ./newsminer/pendingrobots.ibd,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 8192, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
110503 19:39:11  InnoDB: Assertion failure in thread 140331611248400 in file fil/fil0fil.c line 4686
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
110503 19:39:11 - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=33554432
read_buffer_size=2097152
max_used_connections=2
max_threads=500
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2086162 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = (nil) thread_stack 0x30000
/usr/local/mysql51/libexec/mysqld(my_print_stacktrace+0x29) [0x887c49]
/usr/local/mysql51/libexec/mysqld(handle_segfault+0x40d) [0x5abacd]
/lib/libpthread.so.0(+0xf8f0) [0x7fa640ad58f0]
/lib/libc.so.6(gsignal+0x35) [0x7fa63f971a75]
/lib/libc.so.6(abort+0x180) [0x7fa63f9755c0]
/usr/local/mysql51/libexec/mysqld() [0x813ddf]
/usr/local/mysql51/libexec/mysqld() [0x7f2aaf]
/usr/local/mysql51/libexec/mysqld() [0x7f2fd4]
/usr/local/mysql51/libexec/mysqld() [0x7eb11c]
/usr/local/mysql51/libexec/mysqld() [0x7d6b5b]
/usr/local/mysql51/libexec/mysqld() [0x795327]
/usr/local/mysql51/libexec/mysqld() [0x7939f3]
/usr/local/mysql51/libexec/mysqld() [0x794443]
/usr/local/mysql51/libexec/mysqld() [0x794da4]
/usr/local/mysql51/libexec/mysqld() [0x77fc6d]
/usr/local/mysql51/libexec/mysqld() [0x7af1ae]
/usr/local/mysql51/libexec/mysqld() [0x7a5bab]
/lib/libpthread.so.0(+0x69ca) [0x7fa640acc9ca]
/lib/libc.so.6(clone+0x6d) [0x7fa63fa246fd]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
110503 19:39:11 mysqld_safe Number of processes running now: 0
110503 19:39:11 mysqld_safe mysqld restarted
InnoDB: Warning: innodb_overwrite_relay_log_info is enabled. Updates in other storage engines may have problem with consistency.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3
110503 19:39:12  InnoDB: highest supported file format is Barracuda.
110503 19:39:13 Percona XtraDB (http://www.percona.com) 1.0.8-11.2 started; log sequence number 8298149359628
InnoDB: something wrong with relay-info.log. InnoDB will not overwrite it.
110503 19:39:13 [Note] Recovering after a crash using mysql-bin
110503 19:39:13 [Note] Starting crash recovery...
110503 19:39:13 [Note] Crash recovery finished.
110503 19:39:13 [Note] Event Scheduler: Loaded 0 events
110503 19:39:13 [Note] /usr/local/mysql51/libexec/mysqld: ready for connections.
Version: '5.1.47-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
110503 19:39:23  InnoDB: Error: page 4 log sequence number 8299215792744
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:39:23  InnoDB: Error: page 1 log sequence number 8299215891574
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:39:23  InnoDB: Error: page 20 log sequence number 8299215528487
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:39:23  InnoDB: Error: page 106216 log sequence number 8299348330353
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:39:23  InnoDB: Error: page 98305 log sequence number 8299434590706
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:39:23  InnoDB: Error: page 5 log sequence number 8299215789101
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:39:23  InnoDB: Error: page 114689 log sequence number 8299405235524
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:39:23  InnoDB: Error: page 6 log sequence number 8299215192961
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:39:23  InnoDB: Error: page 41756 log sequence number 8299307763762
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:39:23  InnoDB: Error: page 40961 log sequence number 8299348114573
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:39:23  InnoDB: Error: page 3 log sequence number 8299215891509
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Error: trying to access page number 1768711273 in space 995,
InnoDB: space name ./newsminer/pendingrobots.ibd,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 8192, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
110503 19:39:23  InnoDB: Assertion failure in thread 139764892157712 in file fil/fil0fil.c line 4686
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
110503 19:39:23 - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=33554432
read_buffer_size=2097152
max_used_connections=2
max_threads=500
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2086162 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = (nil) thread_stack 0x30000
/usr/local/mysql51/libexec/mysqld(my_print_stacktrace+0x29) [0x887c49]
/usr/local/mysql51/libexec/mysqld(handle_segfault+0x40d) [0x5abacd]
/lib/libpthread.so.0(+0xf8f0) [0x7f224d9648f0]
/lib/libc.so.6(gsignal+0x35) [0x7f224c800a75]
/lib/libc.so.6(abort+0x180) [0x7f224c8045c0]
/usr/local/mysql51/libexec/mysqld() [0x813ddf]
/usr/local/mysql51/libexec/mysqld() [0x7f2aaf]
/usr/local/mysql51/libexec/mysqld() [0x7f2fd4]
/usr/local/mysql51/libexec/mysqld() [0x7eb11c]
/usr/local/mysql51/libexec/mysqld() [0x7d6b5b]
/usr/local/mysql51/libexec/mysqld() [0x795327]
/usr/local/mysql51/libexec/mysqld() [0x7939f3]
/usr/local/mysql51/libexec/mysqld() [0x794443]
/usr/local/mysql51/libexec/mysqld() [0x794da4]
/usr/local/mysql51/libexec/mysqld() [0x77fc6d]
/usr/local/mysql51/libexec/mysqld() [0x7af1ae]
/usr/local/mysql51/libexec/mysqld() [0x7a5bab]
/lib/libpthread.so.0(+0x69ca) [0x7f224d95b9ca]
/lib/libc.so.6(clone+0x6d) [0x7f224c8b36fd]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
110503 19:39:23 mysqld_safe Number of processes running now: 0
110503 19:39:23 mysqld_safe mysqld restarted
InnoDB: Warning: innodb_overwrite_relay_log_info is enabled. Updates in other storage engines may have problem with consistency.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3
110503 19:39:25  InnoDB: highest supported file format is Barracuda.
110503 19:39:26 Percona XtraDB (http://www.percona.com) 1.0.8-11.2 started; log sequence number 8298149359628
InnoDB: something wrong with relay-info.log. InnoDB will not overwrite it.
110503 19:39:26 [Note] Recovering after a crash using mysql-bin
110503 19:39:26 [Note] Starting crash recovery...
110503 19:39:26 [Note] Crash recovery finished.
110503 19:39:26 [Note] Event Scheduler: Loaded 0 events
110503 19:39:26 [Note] /usr/local/mysql51/libexec/mysqld: ready for connections.
Version: '5.1.47-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
110503 19:39:36  InnoDB: Error: page 4 log sequence number 8299215792744
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:39:36  InnoDB: Error: page 1 log sequence number 8299215891574
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:39:36  InnoDB: Error: page 20 log sequence number 8299215528487
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:39:36  InnoDB: Error: page 106216 log sequence number 8299348330353
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:39:36  InnoDB: Error: page 98305 log sequence number 8299434590706
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:39:36  InnoDB: Error: page 5 log sequence number 8299215789101
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:39:36  InnoDB: Error: page 114689 log sequence number 8299405235524
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:39:36  InnoDB: Error: page 6 log sequence number 8299215192961
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:39:36  InnoDB: Error: page 41756 log sequence number 8299307763762
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:39:36  InnoDB: Error: page 40961 log sequence number 8299348114573
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:39:36  InnoDB: Error: page 3 log sequence number 8299215891509
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Error: trying to access page number 1768711273 in space 995,
InnoDB: space name ./newsminer/pendingrobots.ibd,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 8192, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
110503 19:39:36  InnoDB: Assertion failure in thread 140610717689616 in file fil/fil0fil.c line 4686
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
110503 19:39:36 - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=33554432
read_buffer_size=2097152
max_used_connections=2
max_threads=500
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2086162 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = (nil) thread_stack 0x30000
/usr/local/mysql51/libexec/mysqld(my_print_stacktrace+0x29) [0x887c49]
/usr/local/mysql51/libexec/mysqld(handle_segfault+0x40d) [0x5abacd]
/lib/libpthread.so.0(+0xf8f0) [0x7fe73cb7a8f0]
/lib/libc.so.6(gsignal+0x35) [0x7fe73ba16a75]
/lib/libc.so.6(abort+0x180) [0x7fe73ba1a5c0]
/usr/local/mysql51/libexec/mysqld() [0x813ddf]
/usr/local/mysql51/libexec/mysqld() [0x7f2aaf]
/usr/local/mysql51/libexec/mysqld() [0x7f2fd4]
/usr/local/mysql51/libexec/mysqld() [0x7eb11c]
/usr/local/mysql51/libexec/mysqld() [0x7d6b5b]
/usr/local/mysql51/libexec/mysqld() [0x795327]
/usr/local/mysql51/libexec/mysqld() [0x7939f3]
/usr/local/mysql51/libexec/mysqld() [0x794443]
/usr/local/mysql51/libexec/mysqld() [0x794da4]
/usr/local/mysql51/libexec/mysqld() [0x77fc6d]
/usr/local/mysql51/libexec/mysqld() [0x7af1ae]
/usr/local/mysql51/libexec/mysqld() [0x7a5bab]
/lib/libpthread.so.0(+0x69ca) [0x7fe73cb719ca]
/lib/libc.so.6(clone+0x6d) [0x7fe73bac96fd]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
110503 19:39:36 mysqld_safe Number of processes running now: 0
110503 19:39:36 mysqld_safe mysqld restarted
InnoDB: Warning: innodb_overwrite_relay_log_info is enabled. Updates in other storage engines may have problem with consistency.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3
110503 19:39:37  InnoDB: highest supported file format is Barracuda.
110503 19:39:38 Percona XtraDB (http://www.percona.com) 1.0.8-11.2 started; log sequence number 8298149359628
InnoDB: something wrong with relay-info.log. InnoDB will not overwrite it.
110503 19:39:38 [Note] Recovering after a crash using mysql-bin
110503 19:39:38 [Note] Starting crash recovery...
110503 19:39:38 [Note] Crash recovery finished.
110503 19:39:38 [Note] Event Scheduler: Loaded 0 events
110503 19:39:38 [Note] /usr/local/mysql51/libexec/mysqld: ready for connections.
Version: '5.1.47-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
110503 19:39:48  InnoDB: Error: page 4 log sequence number 8299215792744
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:39:48  InnoDB: Error: page 1 log sequence number 8299215891574
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:39:48  InnoDB: Error: page 20 log sequence number 8299215528487
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:39:48  InnoDB: Error: page 106216 log sequence number 8299348330353
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:39:48  InnoDB: Error: page 98305 log sequence number 8299434590706
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:39:48  InnoDB: Error: page 5 log sequence number 8299215789101
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:39:48  InnoDB: Error: page 114689 log sequence number 8299405235524
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:39:48  InnoDB: Error: page 6 log sequence number 8299215192961
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:39:48  InnoDB: Error: page 41756 log sequence number 8299307763762
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:39:48  InnoDB: Error: page 40961 log sequence number 8299348114573
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:39:48  InnoDB: Error: page 3 log sequence number 8299215891509
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Error: trying to access page number 1768711273 in space 995,
InnoDB: space name ./newsminer/pendingrobots.ibd,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 8192, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
110503 19:39:48  InnoDB: Assertion failure in thread 140523241903888 in file fil/fil0fil.c line 4686
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
110503 19:39:48 - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=33554432
read_buffer_size=2097152
max_used_connections=1
max_threads=500
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2086162 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = (nil) thread_stack 0x30000
/usr/local/mysql51/libexec/mysqld(my_print_stacktrace+0x29) [0x887c49]
/usr/local/mysql51/libexec/mysqld(handle_segfault+0x40d) [0x5abacd]
/lib/libpthread.so.0(+0xf8f0) [0x7fd2dec118f0]
/lib/libc.so.6(gsignal+0x35) [0x7fd2ddaada75]
/lib/libc.so.6(abort+0x180) [0x7fd2ddab15c0]
/usr/local/mysql51/libexec/mysqld() [0x813ddf]
/usr/local/mysql51/libexec/mysqld() [0x7f2aaf]
/usr/local/mysql51/libexec/mysqld() [0x7f2fd4]
/usr/local/mysql51/libexec/mysqld() [0x7eb11c]
/usr/local/mysql51/libexec/mysqld() [0x7d6b5b]
/usr/local/mysql51/libexec/mysqld() [0x795327]
/usr/local/mysql51/libexec/mysqld() [0x7939f3]
/usr/local/mysql51/libexec/mysqld() [0x794443]
/usr/local/mysql51/libexec/mysqld() [0x794da4]
/usr/local/mysql51/libexec/mysqld() [0x77fc6d]
/usr/local/mysql51/libexec/mysqld() [0x7af1ae]
/usr/local/mysql51/libexec/mysqld() [0x7a5bab]
/lib/libpthread.so.0(+0x69ca) [0x7fd2dec089ca]
/lib/libc.so.6(clone+0x6d) [0x7fd2ddb606fd]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
110503 19:39:48 mysqld_safe Number of processes running now: 0
110503 19:39:48 mysqld_safe mysqld restarted
InnoDB: Warning: innodb_overwrite_relay_log_info is enabled. Updates in other storage engines may have problem with consistency.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3
110503 19:39:50  InnoDB: highest supported file format is Barracuda.
110503 19:39:51 Percona XtraDB (http://www.percona.com) 1.0.8-11.2 started; log sequence number 8298149359628
InnoDB: something wrong with relay-info.log. InnoDB will not overwrite it.
110503 19:39:51 [Note] Recovering after a crash using mysql-bin
110503 19:39:51 [Note] Starting crash recovery...
110503 19:39:51 [Note] Crash recovery finished.
110503 19:39:51 [Note] Event Scheduler: Loaded 0 events
110503 19:39:51 [Note] /usr/local/mysql51/libexec/mysqld: ready for connections.
Version: '5.1.47-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
110503 19:40:01  InnoDB: Error: page 4 log sequence number 8299215792744
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:01  InnoDB: Error: page 1 log sequence number 8299215891574
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:01  InnoDB: Error: page 20 log sequence number 8299215528487
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:01  InnoDB: Error: page 106216 log sequence number 8299348330353
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:01  InnoDB: Error: page 98305 log sequence number 8299434590706
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:01  InnoDB: Error: page 5 log sequence number 8299215789101
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:01  InnoDB: Error: page 114689 log sequence number 8299405235524
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:01  InnoDB: Error: page 6 log sequence number 8299215192961
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:01  InnoDB: Error: page 41756 log sequence number 8299307763762
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:01  InnoDB: Error: page 40961 log sequence number 8299348114573
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:01  InnoDB: Error: page 3 log sequence number 8299215891509
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Error: trying to access page number 1768711273 in space 995,
InnoDB: space name ./newsminer/pendingrobots.ibd,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 8192, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
110503 19:40:01  InnoDB: Assertion failure in thread 139686376630032 in file fil/fil0fil.c line 4686
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
110503 19:40:01 - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=33554432
read_buffer_size=2097152
max_used_connections=1
max_threads=500
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2086162 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = (nil) thread_stack 0x30000
/usr/local/mysql51/libexec/mysqld(my_print_stacktrace+0x29) [0x887c49]
/usr/local/mysql51/libexec/mysqld(handle_segfault+0x40d) [0x5abacd]
/lib/libpthread.so.0(+0xf8f0) [0x7f1005b268f0]
/lib/libc.so.6(gsignal+0x35) [0x7f10049c2a75]
/lib/libc.so.6(abort+0x180) [0x7f10049c65c0]
/usr/local/mysql51/libexec/mysqld() [0x813ddf]
/usr/local/mysql51/libexec/mysqld() [0x7f2aaf]
/usr/local/mysql51/libexec/mysqld() [0x7f2fd4]
/usr/local/mysql51/libexec/mysqld() [0x7eb11c]
/usr/local/mysql51/libexec/mysqld() [0x7d6b5b]
/usr/local/mysql51/libexec/mysqld() [0x795327]
/usr/local/mysql51/libexec/mysqld() [0x7939f3]
/usr/local/mysql51/libexec/mysqld() [0x794443]
/usr/local/mysql51/libexec/mysqld() [0x794da4]
/usr/local/mysql51/libexec/mysqld() [0x77fc6d]
/usr/local/mysql51/libexec/mysqld() [0x7af1ae]
/usr/local/mysql51/libexec/mysqld() [0x7a5bab]
/lib/libpthread.so.0(+0x69ca) [0x7f1005b1d9ca]
/lib/libc.so.6(clone+0x6d) [0x7f1004a756fd]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
110503 19:40:01 mysqld_safe Number of processes running now: 0
110503 19:40:01 mysqld_safe mysqld restarted
InnoDB: Warning: innodb_overwrite_relay_log_info is enabled. Updates in other storage engines may have problem with consistency.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3
110503 19:40:02  InnoDB: highest supported file format is Barracuda.
110503 19:40:03 Percona XtraDB (http://www.percona.com) 1.0.8-11.2 started; log sequence number 8298149359628
InnoDB: something wrong with relay-info.log. InnoDB will not overwrite it.
110503 19:40:03 [Note] Recovering after a crash using mysql-bin
110503 19:40:03 [Note] Starting crash recovery...
110503 19:40:03 [Note] Crash recovery finished.
110503 19:40:03 [Note] Event Scheduler: Loaded 0 events
110503 19:40:03 [Note] /usr/local/mysql51/libexec/mysqld: ready for connections.
Version: '5.1.47-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
110503 19:40:13  InnoDB: Error: page 4 log sequence number 8299215792744
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:13  InnoDB: Error: page 1 log sequence number 8299215891574
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:13  InnoDB: Error: page 20 log sequence number 8299215528487
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:13  InnoDB: Error: page 106216 log sequence number 8299348330353
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:13  InnoDB: Error: page 98305 log sequence number 8299434590706
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:13  InnoDB: Error: page 5 log sequence number 8299215789101
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:13  InnoDB: Error: page 114689 log sequence number 8299405235524
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:13  InnoDB: Error: page 6 log sequence number 8299215192961
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:13  InnoDB: Error: page 41756 log sequence number 8299307763762
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:13  InnoDB: Error: page 40961 log sequence number 8299348114573
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:13  InnoDB: Error: page 3 log sequence number 8299215891509
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Error: trying to access page number 1768711273 in space 995,
InnoDB: space name ./newsminer/pendingrobots.ibd,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 8192, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
110503 19:40:13  InnoDB: Assertion failure in thread 139882989709072 in file fil/fil0fil.c line 4686
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
110503 19:40:13 - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=33554432
read_buffer_size=2097152
max_used_connections=2
max_threads=500
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2086162 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = (nil) thread_stack 0x30000
/usr/local/mysql51/libexec/mysqld(my_print_stacktrace+0x29) [0x887c49]
/usr/local/mysql51/libexec/mysqld(handle_segfault+0x40d) [0x5abacd]
/lib/libpthread.so.0(+0xf8f0) [0x7f3dccbfe8f0]
/lib/libc.so.6(gsignal+0x35) [0x7f3dcba9aa75]
/lib/libc.so.6(abort+0x180) [0x7f3dcba9e5c0]
/usr/local/mysql51/libexec/mysqld() [0x813ddf]
/usr/local/mysql51/libexec/mysqld() [0x7f2aaf]
/usr/local/mysql51/libexec/mysqld() [0x7f2fd4]
/usr/local/mysql51/libexec/mysqld() [0x7eb11c]
/usr/local/mysql51/libexec/mysqld() [0x7d6b5b]
/usr/local/mysql51/libexec/mysqld() [0x795327]
/usr/local/mysql51/libexec/mysqld() [0x7939f3]
/usr/local/mysql51/libexec/mysqld() [0x794443]
/usr/local/mysql51/libexec/mysqld() [0x794da4]
/usr/local/mysql51/libexec/mysqld() [0x77fc6d]
/usr/local/mysql51/libexec/mysqld() [0x7af1ae]
/usr/local/mysql51/libexec/mysqld() [0x7a5bab]
/lib/libpthread.so.0(+0x69ca) [0x7f3dccbf59ca]
/lib/libc.so.6(clone+0x6d) [0x7f3dcbb4d6fd]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
110503 19:40:13 mysqld_safe Number of processes running now: 0
110503 19:40:13 mysqld_safe mysqld restarted
InnoDB: Warning: innodb_overwrite_relay_log_info is enabled. Updates in other storage engines may have problem with consistency.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3
110503 19:40:14  InnoDB: highest supported file format is Barracuda.
110503 19:40:15 Percona XtraDB (http://www.percona.com) 1.0.8-11.2 started; log sequence number 8298149359628
InnoDB: something wrong with relay-info.log. InnoDB will not overwrite it.
110503 19:40:15 [Note] Recovering after a crash using mysql-bin
110503 19:40:15 [Note] Starting crash recovery...
110503 19:40:15 [Note] Crash recovery finished.
110503 19:40:15 [Note] Event Scheduler: Loaded 0 events
110503 19:40:15 [Note] /usr/local/mysql51/libexec/mysqld: ready for connections.
Version: '5.1.47-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
110503 19:40:25  InnoDB: Error: page 4 log sequence number 8299215792744
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:25  InnoDB: Error: page 1 log sequence number 8299215891574
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:25  InnoDB: Error: page 20 log sequence number 8299215528487
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:25  InnoDB: Error: page 106216 log sequence number 8299348330353
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:25  InnoDB: Error: page 98305 log sequence number 8299434590706
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:25  InnoDB: Error: page 5 log sequence number 8299215789101
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:25  InnoDB: Error: page 114689 log sequence number 8299405235524
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:25  InnoDB: Error: page 6 log sequence number 8299215192961
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:25  InnoDB: Error: page 41756 log sequence number 8299307763762
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:25  InnoDB: Error: page 40961 log sequence number 8299348114573
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:25  InnoDB: Error: page 3 log sequence number 8299215891509
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Error: trying to access page number 1768711273 in space 995,
InnoDB: space name ./newsminer/pendingrobots.ibd,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 8192, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
110503 19:40:25  InnoDB: Assertion failure in thread 140309091649296 in file fil/fil0fil.c line 4686
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
110503 19:40:25 - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=33554432
read_buffer_size=2097152
max_used_connections=2
max_threads=500
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2086162 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = (nil) thread_stack 0x30000
/usr/local/mysql51/libexec/mysqld(my_print_stacktrace+0x29) [0x887c49]
/usr/local/mysql51/libexec/mysqld(handle_segfault+0x40d) [0x5abacd]
/lib/libpthread.so.0(+0xf8f0) [0x7fa1026788f0]
/lib/libc.so.6(gsignal+0x35) [0x7fa101514a75]
/lib/libc.so.6(abort+0x180) [0x7fa1015185c0]
/usr/local/mysql51/libexec/mysqld() [0x813ddf]
/usr/local/mysql51/libexec/mysqld() [0x7f2aaf]
/usr/local/mysql51/libexec/mysqld() [0x7f2fd4]
/usr/local/mysql51/libexec/mysqld() [0x7eb11c]
/usr/local/mysql51/libexec/mysqld() [0x7d6b5b]
/usr/local/mysql51/libexec/mysqld() [0x795327]
/usr/local/mysql51/libexec/mysqld() [0x7939f3]
/usr/local/mysql51/libexec/mysqld() [0x794443]
/usr/local/mysql51/libexec/mysqld() [0x794da4]
/usr/local/mysql51/libexec/mysqld() [0x77fc6d]
/usr/local/mysql51/libexec/mysqld() [0x7af1ae]
/usr/local/mysql51/libexec/mysqld() [0x7a5bab]
/lib/libpthread.so.0(+0x69ca) [0x7fa10266f9ca]
/lib/libc.so.6(clone+0x6d) [0x7fa1015c76fd]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
110503 19:40:26 mysqld_safe Number of processes running now: 0
110503 19:40:26 mysqld_safe mysqld restarted
InnoDB: Warning: innodb_overwrite_relay_log_info is enabled. Updates in other storage engines may have problem with consistency.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3
110503 19:40:27  InnoDB: highest supported file format is Barracuda.
110503 19:40:28 Percona XtraDB (http://www.percona.com) 1.0.8-11.2 started; log sequence number 8298149359628
InnoDB: something wrong with relay-info.log. InnoDB will not overwrite it.
110503 19:40:28 [Note] Recovering after a crash using mysql-bin
110503 19:40:28 [Note] Starting crash recovery...
110503 19:40:28 [Note] Crash recovery finished.
110503 19:40:28 [Note] Event Scheduler: Loaded 0 events
110503 19:40:28 [Note] /usr/local/mysql51/libexec/mysqld: ready for connections.
Version: '5.1.47-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
110503 19:40:38  InnoDB: Error: page 4 log sequence number 8299215792744
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:38  InnoDB: Error: page 1 log sequence number 8299215891574
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:38  InnoDB: Error: page 20 log sequence number 8299215528487
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:38  InnoDB: Error: page 106216 log sequence number 8299348330353
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:38  InnoDB: Error: page 98305 log sequence number 8299434590706
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:38  InnoDB: Error: page 5 log sequence number 8299215789101
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:38  InnoDB: Error: page 114689 log sequence number 8299405235524
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:38  InnoDB: Error: page 6 log sequence number 8299215192961
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:38  InnoDB: Error: page 41756 log sequence number 8299307763762
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:38  InnoDB: Error: page 40961 log sequence number 8299348114573
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:38  InnoDB: Error: page 3 log sequence number 8299215891509
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Error: trying to access page number 1768711273 in space 995,
InnoDB: space name ./newsminer/pendingrobots.ibd,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 8192, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
110503 19:40:38  InnoDB: Assertion failure in thread 140704606127888 in file fil/fil0fil.c line 4686
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
110503 19:40:38 - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=33554432
read_buffer_size=2097152
max_used_connections=1
max_threads=500
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2086162 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = (nil) thread_stack 0x30000
/usr/local/mysql51/libexec/mysqld(my_print_stacktrace+0x29) [0x887c49]
/usr/local/mysql51/libexec/mysqld(handle_segfault+0x40d) [0x5abacd]
/lib/libpthread.so.0(+0xf8f0) [0x7ffd18e788f0]
/lib/libc.so.6(gsignal+0x35) [0x7ffd17d14a75]
/lib/libc.so.6(abort+0x180) [0x7ffd17d185c0]
/usr/local/mysql51/libexec/mysqld() [0x813ddf]
/usr/local/mysql51/libexec/mysqld() [0x7f2aaf]
/usr/local/mysql51/libexec/mysqld() [0x7f2fd4]
/usr/local/mysql51/libexec/mysqld() [0x7eb11c]
/usr/local/mysql51/libexec/mysqld() [0x7d6b5b]
/usr/local/mysql51/libexec/mysqld() [0x795327]
/usr/local/mysql51/libexec/mysqld() [0x7939f3]
/usr/local/mysql51/libexec/mysqld() [0x794443]
/usr/local/mysql51/libexec/mysqld() [0x794da4]
/usr/local/mysql51/libexec/mysqld() [0x77fc6d]
/usr/local/mysql51/libexec/mysqld() [0x7af1ae]
/usr/local/mysql51/libexec/mysqld() [0x7a5bab]
/lib/libpthread.so.0(+0x69ca) [0x7ffd18e6f9ca]
/lib/libc.so.6(clone+0x6d) [0x7ffd17dc76fd]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
110503 19:40:38 mysqld_safe Number of processes running now: 0
110503 19:40:38 mysqld_safe mysqld restarted
InnoDB: Warning: innodb_overwrite_relay_log_info is enabled. Updates in other storage engines may have problem with consistency.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3
110503 19:40:39  InnoDB: highest supported file format is Barracuda.
110503 19:40:40 Percona XtraDB (http://www.percona.com) 1.0.8-11.2 started; log sequence number 8298149359628
InnoDB: something wrong with relay-info.log. InnoDB will not overwrite it.
110503 19:40:40 [Note] Recovering after a crash using mysql-bin
110503 19:40:40 [Note] Starting crash recovery...
110503 19:40:40 [Note] Crash recovery finished.
110503 19:40:40 [Note] Event Scheduler: Loaded 0 events
110503 19:40:40 [Note] /usr/local/mysql51/libexec/mysqld: ready for connections.
Version: '5.1.47-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
110503 19:40:50  InnoDB: Error: page 4 log sequence number 8299215792744
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:50  InnoDB: Error: page 1 log sequence number 8299215891574
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:50  InnoDB: Error: page 20 log sequence number 8299215528487
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:50  InnoDB: Error: page 106216 log sequence number 8299348330353
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:50  InnoDB: Error: page 98305 log sequence number 8299434590706
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:50  InnoDB: Error: page 5 log sequence number 8299215789101
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:50  InnoDB: Error: page 114689 log sequence number 8299405235524
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:50  InnoDB: Error: page 6 log sequence number 8299215192961
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:50  InnoDB: Error: page 41756 log sequence number 8299307763762
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:50  InnoDB: Error: page 40961 log sequence number 8299348114573
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:50  InnoDB: Error: page 3 log sequence number 8299215891509
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Error: trying to access page number 1768711273 in space 995,
InnoDB: space name ./newsminer/pendingrobots.ibd,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 8192, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
110503 19:40:50  InnoDB: Assertion failure in thread 139818256340752 in file fil/fil0fil.c line 4686
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
110503 19:40:50 - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=33554432
read_buffer_size=2097152
max_used_connections=2
max_threads=500
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2086162 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = (nil) thread_stack 0x30000
/usr/local/mysql51/libexec/mysqld(my_print_stacktrace+0x29) [0x887c49]
/usr/local/mysql51/libexec/mysqld(handle_segfault+0x40d) [0x5abacd]
/lib/libpthread.so.0(+0xf8f0) [0x7f2eba5718f0]
/lib/libc.so.6(gsignal+0x35) [0x7f2eb940da75]
/lib/libc.so.6(abort+0x180) [0x7f2eb94115c0]
/usr/local/mysql51/libexec/mysqld() [0x813ddf]
/usr/local/mysql51/libexec/mysqld() [0x7f2aaf]
/usr/local/mysql51/libexec/mysqld() [0x7f2fd4]
/usr/local/mysql51/libexec/mysqld() [0x7eb11c]
/usr/local/mysql51/libexec/mysqld() [0x7d6b5b]
/usr/local/mysql51/libexec/mysqld() [0x795327]
/usr/local/mysql51/libexec/mysqld() [0x7939f3]
/usr/local/mysql51/libexec/mysqld() [0x794443]
/usr/local/mysql51/libexec/mysqld() [0x794da4]
/usr/local/mysql51/libexec/mysqld() [0x77fc6d]
/usr/local/mysql51/libexec/mysqld() [0x7af1ae]
/usr/local/mysql51/libexec/mysqld() [0x7a5bab]
/lib/libpthread.so.0(+0x69ca) [0x7f2eba5689ca]
/lib/libc.so.6(clone+0x6d) [0x7f2eb94c06fd]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
110503 19:40:51 mysqld_safe Number of processes running now: 0
110503 19:40:51 mysqld_safe mysqld restarted
InnoDB: Warning: innodb_overwrite_relay_log_info is enabled. Updates in other storage engines may have problem with consistency.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3
110503 19:40:52  InnoDB: highest supported file format is Barracuda.
110503 19:40:53 Percona XtraDB (http://www.percona.com) 1.0.8-11.2 started; log sequence number 8298149359628
InnoDB: something wrong with relay-info.log. InnoDB will not overwrite it.
110503 19:40:53 [Note] Recovering after a crash using mysql-bin
110503 19:40:53 [Note] Starting crash recovery...
110503 19:40:53 [Note] Crash recovery finished.
110503 19:40:53 [Note] Event Scheduler: Loaded 0 events
110503 19:40:53 [Note] /usr/local/mysql51/libexec/mysqld: ready for connections.
Version: '5.1.47-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
110503 19:40:55  InnoDB: Error: page 3 log sequence number 8298958608559
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 1 log sequence number 8298963081528
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 2 log sequence number 8298958702020
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 65537 log sequence number 8298973459449
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 237569 log sequence number 8298920689963
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 98305 log sequence number 8299049892189
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 163841 log sequence number 8299064174221
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 131073 log sequence number 8299144611278
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 73729 log sequence number 8298941104781
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 66386 log sequence number 8299001212514
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 106497 log sequence number 8299057583435
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 229377 log sequence number 8298997979492
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 4 log sequence number 8298907130453
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 142162 log sequence number 8298541794972
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 139265 log sequence number 8299024179762
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 196609 log sequence number 8299077363388
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 16417 log sequence number 8298347103833
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 16385 log sequence number 8298999777533
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 32769 log sequence number 8298941131085
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 72767 log sequence number 8298347901765
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 90113 log sequence number 8299024225952
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 72761 log sequence number 8298572700663
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 72722 log sequence number 8298907414802
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 142145 log sequence number 8298830071112
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 49153 log sequence number 8298993310905
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 72731 log sequence number 8298911198117
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 5 log sequence number 8298958702020
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 204988 log sequence number 8299077451179
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 204801 log sequence number 8299113809161
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 76879 log sequence number 8298986688674
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 172033 log sequence number 8299122916604
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 40961 log sequence number 8298913972048
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 6 log sequence number 8298897500335
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 24577 log sequence number 8298927501898
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 180225 log sequence number 8299094120836
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 122881 log sequence number 8299008547705
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 24620 log sequence number 8298897500335
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 155649 log sequence number 8299147113235
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 57345 log sequence number 8299001173412
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 221185 log sequence number 8299167970853
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 7 log sequence number 8298947920990
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 181654 log sequence number 8298729901214
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 181634 log sequence number 8298613183044
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 8242 log sequence number 8298679304891
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 8193 log sequence number 8298922811612
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 16427 log sequence number 8298536532336
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 70264 log sequence number 8299014454029
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 8 log sequence number 8298949503246
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 9 log sequence number 8298911431314
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 114689 log sequence number 8299000882420
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 117952 log sequence number 8299008679661
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 147457 log sequence number 8299160548686
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 177983 log sequence number 8299022721528
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 1 log sequence number 8300297956402
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 3 log sequence number 8300733747078
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 1 log sequence number 8300776777403
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:55  InnoDB: Error: page 2 log sequence number 8300733747078
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 8193 log sequence number 8300853586603
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 230 log sequence number 8300890381756
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 227 log sequence number 8300733610024
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 4993 log sequence number 8300726329391
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 9841 log sequence number 8300799080008
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 3 log sequence number 8300505006197
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 1 log sequence number 8300605953327
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 2 log sequence number 8300627113778
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 24577 log sequence number 8300788133828
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 16385 log sequence number 8300634424149
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 8193 log sequence number 8300627112838
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 49153 log sequence number 8300784225003
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 40961 log sequence number 8300785495681
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 32769 log sequence number 8300783492926
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 4 log sequence number 8300095285419
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 73729 log sequence number 8300833972713
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 66727 log sequence number 8299455961726
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 65537 log sequence number 8300794848520
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 5 log sequence number 8300627113778
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 8238 log sequence number 8300627113778
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 90113 log sequence number 8300892290166
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 81921 log sequence number 8300828227429
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 74402 log sequence number 8300760270471
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 74862 log sequence number 8300744922370
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 3 log sequence number 8299140870246
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 1 log sequence number 8299150858531
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 2 log sequence number 8299147454440
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 18 log sequence number 8299150856180
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 2351 log sequence number 8299236629943
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 4 log sequence number 8299141017961
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 778 log sequence number 8299117570353
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 793 log sequence number 8298854085852
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 782 log sequence number 8299011862935
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 790 log sequence number 8298382684305
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 5 log sequence number 8299148465501
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 2184 log sequence number 8299129975349
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 2302 log sequence number 8299131589016
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 2180 log sequence number 8299131589016
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 2277 log sequence number 8298842649317
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 2191 log sequence number 8299145104204
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 6 log sequence number 8299141526030
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 1272 log sequence number 8298647097653
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 3258 log sequence number 8299153409473
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 3234 log sequence number 8299134064205
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 3278 log sequence number 8299219367822
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 37 log sequence number 8298848009822
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 3 log sequence number 8299783124614
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 1 log sequence number 8299911070689
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 2 log sequence number 8299783124614
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 518 log sequence number 8299924253414
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 1517 log sequence number 8299924253414
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 1 log sequence number 8298374790760
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 140 log sequence number 8298374790723
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 804893 log sequence number 8298270841930
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 802817 log sequence number 8298216067343
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 1130497 log sequence number 8298557922349
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 1073153 log sequence number 8298563566573
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 1212417 log sequence number 8298773352790
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 1196033 log sequence number 8298765144994
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:56  InnoDB: Error: page 983041 log sequence number 8298364287530
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:57  InnoDB: Error: page 1081345 log sequence number 8298643219191
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:57  InnoDB: Error: page 1138689 log sequence number 8298686664054
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:57  InnoDB: Error: page 1097729 log sequence number 8298626222542
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:57  InnoDB: Error: page 851969 log sequence number 8298162443378
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:57  InnoDB: Error: page 1105921 log sequence number 8298663735530
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:57  InnoDB: Error: page 1143105 log sequence number 8298579043300
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:57  InnoDB: Error: page 778241 log sequence number 8298169337608
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:57  InnoDB: Error: page 1122305 log sequence number 8298534445606
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:57  InnoDB: Error: page 1318913 log sequence number 8298848444188
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:57  InnoDB: Error: page 942081 log sequence number 8298361495918
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:57  InnoDB: Error: page 1187841 log sequence number 8298674437097
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:57  InnoDB: Error: page 1048577 log sequence number 8298576663383
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:57  InnoDB: Error: page 1163265 log sequence number 8298726424046
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:57  InnoDB: Error: page 901121 log sequence number 8298350177509
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 1490945 log sequence number 8299009930381
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 1040385 log sequence number 8298495759409
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 1204225 log sequence number 8298438411493
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 1384449 log sequence number 8298962533854
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 1187841 log sequence number 8298745196407
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 966657 log sequence number 8298454282333
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 958465 log sequence number 8298330877795
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 1409025 log sequence number 8299005232479
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 1410958 log sequence number 8298438411757
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 1007617 log sequence number 8298447771385
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 1400833 log sequence number 8299048261949
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 1064961 log sequence number 8298388934250
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 1528019 log sequence number 8298226142161
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 1523713 log sequence number 8299160397224
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 1460022 log sequence number 8298838066321
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 1458177 log sequence number 8298971871266
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 909313 log sequence number 8298303130804
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 848187 log sequence number 8298157947794
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 843777 log sequence number 8298192657506
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 3 log sequence number 8299143817851
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 1 log sequence number 8299466185023
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 2 log sequence number 8299251415098
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 42 log sequence number 8299143817851
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 5984 log sequence number 8299143817851
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 4 log sequence number 8298362960019
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 8 log sequence number 8298362960019
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 5 log sequence number 8299251415098
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 108 log sequence number 8299251415098
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 576 log sequence number 8298635384939
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 114 log sequence number 8298476095987
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 202 log sequence number 8299055641797
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 116 log sequence number 8299251233485
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 992 log sequence number 8298743575173
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 5985 log sequence number 8299466184912
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 3 log sequence number 8299153816705
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 2 log sequence number 8299153816705
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 26 log sequence number 8299001839949
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 32769 log sequence number 8299156980138
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 3 log sequence number 8299215891509
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 1 log sequence number 8299215891574
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 2 log sequence number 8299215891509
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 106497 log sequence number 8299412534438
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 28 log sequence number 8299215902042
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 113255 log sequence number 8299303262485
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 26 log sequence number 8299215785032
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 8193 log sequence number 8299350817950
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 4 log sequence number 8299215792744
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 10 log sequence number 8299215528607
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 62132 log sequence number 8299419370295
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 57345 log sequence number 8299349357306
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 9 log sequence number 8299214810822
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 99418 log sequence number 8299465988920
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 98305 log sequence number 8299434590706
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 21 log sequence number 8299215792864
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 20 log sequence number 8299215528487
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 40961 log sequence number 8299348114573
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 73729 log sequence number 8299407100162
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 35703 log sequence number 8299339776278
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 32769 log sequence number 8299350811407
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 5 log sequence number 8299215789101
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 114689 log sequence number 8299405235524
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 6 log sequence number 8299215192961
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 41738 log sequence number 8299289699452
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 3 log sequence number 8299503610512
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 2 log sequence number 8299503610512
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 155649 log sequence number 8299738524983
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 278529 log sequence number 8299788248595
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 360449 log sequence number 8299829756920
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 73729 log sequence number 8298462478003
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:58  InnoDB: Error: page 4 log sequence number 8299502099496
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 270337 log sequence number 8299820291925
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 188417 log sequence number 8299387417832
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 319489 log sequence number 8299818418995
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 139265 log sequence number 8299533491426
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 349736 log sequence number 8299634965731
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 393882 log sequence number 8299635364775
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 393217 log sequence number 8299906612441
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 3 log sequence number 8300650484110
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 1 log sequence number 8300799235810
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 2 log sequence number 8300650484110
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 5 log sequence number 8300678862741
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 795 log sequence number 8300799235732
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 3 log sequence number 8298823539310
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 1 log sequence number 8298823444257
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 2 log sequence number 8298823539310
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 11 log sequence number 8298822600671
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 12 log sequence number 8298823539310
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 4 log sequence number 8298823444257
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 42 log sequence number 8298823088022
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 1982 log sequence number 8298816743447
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 134 log sequence number 8298823089063
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 1938 log sequence number 8298821142660
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 46 log sequence number 8298823444257
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 503 log sequence number 8298812049993
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 45 log sequence number 8298823508413
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 1926 log sequence number 8298822606040
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 2056 log sequence number 8298816758436
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 1733 log sequence number 8298811044198
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 791 log sequence number 8298819169847
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 1283 log sequence number 8298810521129
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 1661 log sequence number 8298823636553
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 661 log sequence number 8299136468584
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 532 log sequence number 8299387917071
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 547 log sequence number 8299138301623
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 182 log sequence number 8299229368487
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 136 log sequence number 8299207699009
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 672 log sequence number 8299412136006
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 173 log sequence number 8299152517664
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 217 log sequence number 8299067614061
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 3 log sequence number 8298526199357
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 3 log sequence number 8298526205051
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 3 log sequence number 8299416403156
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 3 log sequence number 8299373629418
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 2 log sequence number 8299373647384
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 819201 log sequence number 8300390314324
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 892929 log sequence number 8300494951443
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 917505 log sequence number 8300391117213
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 647169 log sequence number 8299703344092
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 4 log sequence number 8299373282914
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 704513 log sequence number 8299182565564
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 5 log sequence number 8299277685717
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 6 log sequence number 8299373647384
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:40:59  InnoDB: Error: page 835585 log sequence number 8300271171909
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 532481 log sequence number 8298280497406
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 802817 log sequence number 8300396910226
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 761857 log sequence number 8300271168133
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 3 log sequence number 8299806351592
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 2 log sequence number 8299806351592
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 3 log sequence number 8298202318613
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 1 log sequence number 8298202268827
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 2 log sequence number 8298210033929
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 1282031 log sequence number 8299688130147
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 1277953 log sequence number 8299646121674
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 2408449 log sequence number 8301159089039
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 2433025 log sequence number 8301261157758
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 2613249 log sequence number 8301405943104
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 2621441 log sequence number 8301325546429
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 2195457 log sequence number 8300940909904
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 2293761 log sequence number 8301108524289
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 2826241 log sequence number 8301609889489
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 2875393 log sequence number 8301722640655
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 1351681 log sequence number 8299646055484
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 1392641 log sequence number 8299819092591
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 393217 log sequence number 8298448278751
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 425985 log sequence number 8298335195389
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 1286145 log sequence number 8299757487969
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 4 log sequence number 8298202276649
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 1703937 log sequence number 8300245752111
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 786433 log sequence number 8299132884069
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 1613825 log sequence number 8300143690795
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 2736129 log sequence number 8301435230133
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 1761281 log sequence number 8300410179280
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 155649 log sequence number 8298231011946
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 2252801 log sequence number 8300892776942
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 1130497 log sequence number 8299425654804
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 1425409 log sequence number 8299709869283
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 2637825 log sequence number 8301359027685
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 860161 log sequence number 8298997859808
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 5 log sequence number 8298210033929
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 704513 log sequence number 8298350476994
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 2072577 log sequence number 8300745429140
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 2973697 log sequence number 8301712851633
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 229377 log sequence number 8298376350854
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 1081345 log sequence number 8298751111511
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 811009 log sequence number 8298789319743
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 638977 log sequence number 8298902770937
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 778241 log sequence number 8298919857218
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 475137 log sequence number 8298351161303
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 573441 log sequence number 8298829301152
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 1925121 log sequence number 8300540248737
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 2228225 log sequence number 8300986833677
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 843777 log sequence number 8299023337518
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 1990657 log sequence number 8300637536076
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 6 log sequence number 8298186754696
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 303105 log sequence number 8298237545611
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 2703361 log sequence number 8301409486422
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 2686977 log sequence number 8301418554415
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 2244609 log sequence number 8301037373519
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 1228801 log sequence number 8299578552060
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 827393 log sequence number 8298335096504
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 835585 log sequence number 8298985602459
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 1040385 log sequence number 8299292786916
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 2310145 log sequence number 8301021968868
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 286721 log sequence number 8298376180790
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 966657 log sequence number 8298922779894
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 1310721 log sequence number 8299832462818
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 2682891 log sequence number 8300977762799
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 2678785 log sequence number 8301510798391
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 1024001 log sequence number 8299014298160
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 1490945 log sequence number 8299880691195
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 1687553 log sequence number 8300216187735
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 417793 log sequence number 8298197370027
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 1114113 log sequence number 8299379993106
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 3145729 log sequence number 8301799339595
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 2064385 log sequence number 8300637632595
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 2719745 log sequence number 8301494171398
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 8 log sequence number 8298197979460
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:00  InnoDB: Error: page 1458177 log sequence number 8299717221544
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01  InnoDB: Error: page 2057220 log sequence number 8299604294976
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01  InnoDB: Error: page 2056193 log sequence number 8300655932375
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01  InnoDB: Error: page 2252333 log sequence number 8299185974365
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01  InnoDB: Error: page 958465 log sequence number 8299298523192
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01  InnoDB: Error: page 450561 log sequence number 8298683639011
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01  InnoDB: Error: page 294913 log sequence number 8298474522735
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01  InnoDB: Error: page 32769 log sequence number 8298175878380
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01  InnoDB: Error: page 2057231 log sequence number 8298241901305
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01  InnoDB: Error: page 2359297 log sequence number 8301036314359
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01  InnoDB: Error: page 9 log sequence number 8298169204565
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01  InnoDB: Error: page 1281618 log sequence number 8298433710032
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01  InnoDB: Error: page 376833 log sequence number 8298154211634
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01  InnoDB: Error: page 2843311 log sequence number 8299381639571
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01  InnoDB: Error: page 2842625 log sequence number 8301673120065
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01  InnoDB: Error: page 2031617 log sequence number 8300734653324
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01  InnoDB: Error: page 1889429 log sequence number 8299340204188
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01  InnoDB: Error: page 1884161 log sequence number 8300540743827
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01  InnoDB: Error: page 1499137 log sequence number 8299844613104
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01  InnoDB: Error: page 1064961 log sequence number 8299469277808
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01  InnoDB: Error: page 237569 log sequence number 8298376180715
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01  InnoDB: Error: page 1542415 log sequence number 8299204964750
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01  InnoDB: Error: page 1540097 log sequence number 8299958160847
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01  InnoDB: Error: page 10 log sequence number 8298169331808
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01  InnoDB: Error: page 1032193 log sequence number 8298951332679
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01  InnoDB: Error: page 3063809 log sequence number 8301845465021
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01  InnoDB: Error: page 2210663 log sequence number 8299123702029
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01  InnoDB: Error: page 2203649 log sequence number 8300953382865
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01  InnoDB: Error: page 2342913 log sequence number 8301053668837
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01  InnoDB: Error: page 1187841 log sequence number 8299573310754
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01  InnoDB: Error: page 1630209 log sequence number 8300087339116
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01  InnoDB: Error: page 2236417 log sequence number 8300978510290
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01  InnoDB: Error: page 311297 log sequence number 8298218187806
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01  InnoDB: Error: page 1400833 log sequence number 8299595202903
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01  InnoDB: Error: page 2564097 log sequence number 8301319030686
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01  InnoDB: Error: page 81921 log sequence number 8298259266527
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01  InnoDB: Error: page 598017 log sequence number 8298792787633
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01  InnoDB: Error: page 802817 log sequence number 8299023436014
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01  InnoDB: Error: page 12 log sequence number 8298172208091
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01  InnoDB: Error: page 1007617 log sequence number 8299283566094
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01  InnoDB: Error: page 352257 log sequence number 8298350283036
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01  InnoDB: Error: page 2449409 log sequence number 8301203521230
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01  InnoDB: Error: page 2138113 log sequence number 8300905717780
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01  InnoDB: Error: page 90113 log sequence number 8298326853010
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01  InnoDB: Error: page 1122305 log sequence number 8299533790065
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01  InnoDB: Error: page 114689 log sequence number 8298316720267
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:01 - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=33554432
read_buffer_size=2097152
max_used_connections=3
max_threads=500
threads_connected=1
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2086162 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x1e4f6680
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0x7f61a1d67e58 thread_stack 0x30000
/usr/local/mysql51/libexec/mysqld(my_print_stacktrace+0x29) [0x887c49]
/usr/local/mysql51/libexec/mysqld(handle_segfault+0x40d) [0x5abacd]
/lib/libpthread.so.0(+0xf8f0) [0x7f61a19488f0]
/usr/local/mysql51/libexec/mysqld() [0x772209]
/usr/local/mysql51/libexec/mysqld() [0x7d6334]
/usr/local/mysql51/libexec/mysqld() [0x79820a]
/usr/local/mysql51/libexec/mysqld() [0x740f45]
/usr/local/mysql51/libexec/mysqld() [0x743825]
/usr/local/mysql51/libexec/mysqld(handler::ha_open(st_table*, char const*, int, int)+0x3d) [0x69f4ad]
/usr/local/mysql51/libexec/mysqld(open_table_from_share(THD*, st_table_share*, char const*, unsigned int, unsigned int, unsigned int, st_table*, bool)+0x50e) [0x5fed6e]
/usr/local/mysql51/libexec/mysqld() [0x5f8dd5]
/usr/local/mysql51/libexec/mysqld(open_table(THD*, TABLE_LIST*, st_mem_root*, bool*, unsigned int)+0x845) [0x5fa025]
/usr/local/mysql51/libexec/mysqld(open_tables(THD*, TABLE_LIST**, unsigned int*, unsigned int)+0x684) [0x5fac14]
/usr/local/mysql51/libexec/mysqld(open_normal_and_derived_tables(THD*, TABLE_LIST*, unsigned int)+0x1e) [0x5fad8e]
/usr/local/mysql51/libexec/mysqld(mysqld_list_fields(THD*, TABLE_LIST*, char const*)+0x1e) [0x6c56fe]
/usr/local/mysql51/libexec/mysqld(dispatch_command(enum_server_command, THD*, char*, unsigned int)+0xd2e) [0x5c28ce]
/usr/local/mysql51/libexec/mysqld(do_command(THD*)+0x12a) [0x5c328a]
/usr/local/mysql51/libexec/mysqld(handle_one_connection+0x350) [0x5b5640]
/lib/libpthread.so.0(+0x69ca) [0x7f61a193f9ca]
/lib/libc.so.6(clone+0x6d) [0x7f61a08976fd]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x1e553400 = 
thd->thread_id=1
thd->killed=NOT_KILLED
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
110503 19:41:01 mysqld_safe Number of processes running now: 0
110503 19:41:01 mysqld_safe mysqld restarted
InnoDB: Warning: innodb_overwrite_relay_log_info is enabled. Updates in other storage engines may have problem with consistency.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3
110503 19:41:02  InnoDB: highest supported file format is Barracuda.
110503 19:41:04 Percona XtraDB (http://www.percona.com) 1.0.8-11.2 started; log sequence number 8298149359628
InnoDB: something wrong with relay-info.log. InnoDB will not overwrite it.
110503 19:41:04 [Note] Recovering after a crash using mysql-bin
110503 19:41:04 [Note] Starting crash recovery...
110503 19:41:04 [Note] Crash recovery finished.
110503 19:41:04 [Note] Event Scheduler: Loaded 0 events
110503 19:41:04 [Note] /usr/local/mysql51/libexec/mysqld: ready for connections.
Version: '5.1.47-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
110503 19:41:14  InnoDB: Error: page 4 log sequence number 8299215792744
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:14  InnoDB: Error: page 1 log sequence number 8299215891574
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:14  InnoDB: Error: page 20 log sequence number 8299215528487
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:14  InnoDB: Error: page 106216 log sequence number 8299348330353
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:14  InnoDB: Error: page 98305 log sequence number 8299434590706
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:14  InnoDB: Error: page 5 log sequence number 8299215789101
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:14  InnoDB: Error: page 114689 log sequence number 8299405235524
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:14  InnoDB: Error: page 6 log sequence number 8299215192961
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:14  InnoDB: Error: page 41756 log sequence number 8299307763762
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:14  InnoDB: Error: page 40961 log sequence number 8299348114573
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:14  InnoDB: Error: page 3 log sequence number 8299215891509
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Error: trying to access page number 1768711273 in space 995,
InnoDB: space name ./newsminer/pendingrobots.ibd,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 8192, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
110503 19:41:14  InnoDB: Assertion failure in thread 139705880049424 in file fil/fil0fil.c line 4686
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
110503 19:41:14 - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=33554432
read_buffer_size=2097152
max_used_connections=2
max_threads=500
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2086162 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = (nil) thread_stack 0x30000
/usr/local/mysql51/libexec/mysqld(my_print_stacktrace+0x29) [0x887c49]
/usr/local/mysql51/libexec/mysqld(handle_segfault+0x40d) [0x5abacd]
/lib/libpthread.so.0(+0xf8f0) [0x7f149030f8f0]
/lib/libc.so.6(gsignal+0x35) [0x7f148f1aba75]
/lib/libc.so.6(abort+0x180) [0x7f148f1af5c0]
/usr/local/mysql51/libexec/mysqld() [0x813ddf]
/usr/local/mysql51/libexec/mysqld() [0x7f2aaf]
/usr/local/mysql51/libexec/mysqld() [0x7f2fd4]
/usr/local/mysql51/libexec/mysqld() [0x7eb11c]
/usr/local/mysql51/libexec/mysqld() [0x7d6b5b]
/usr/local/mysql51/libexec/mysqld() [0x795327]
/usr/local/mysql51/libexec/mysqld() [0x7939f3]
/usr/local/mysql51/libexec/mysqld() [0x794443]
/usr/local/mysql51/libexec/mysqld() [0x794da4]
/usr/local/mysql51/libexec/mysqld() [0x77fc6d]
/usr/local/mysql51/libexec/mysqld() [0x7af1ae]
/usr/local/mysql51/libexec/mysqld() [0x7a5bab]
/lib/libpthread.so.0(+0x69ca) [0x7f14903069ca]
/lib/libc.so.6(clone+0x6d) [0x7f148f25e6fd]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
110503 19:41:14 mysqld_safe Number of processes running now: 0
110503 19:41:14 mysqld_safe mysqld restarted
InnoDB: Warning: innodb_overwrite_relay_log_info is enabled. Updates in other storage engines may have problem with consistency.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3
110503 19:41:15  InnoDB: highest supported file format is Barracuda.
110503 19:41:16 Percona XtraDB (http://www.percona.com) 1.0.8-11.2 started; log sequence number 8298149359628
InnoDB: something wrong with relay-info.log. InnoDB will not overwrite it.
110503 19:41:16 [Note] Recovering after a crash using mysql-bin
110503 19:41:16 [Note] Starting crash recovery...
110503 19:41:16 [Note] Crash recovery finished.
110503 19:41:16 [Note] Event Scheduler: Loaded 0 events
110503 19:41:16 [Note] /usr/local/mysql51/libexec/mysqld: ready for connections.
Version: '5.1.47-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
110503 19:41:26  InnoDB: Error: page 4 log sequence number 8299215792744
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:26  InnoDB: Error: page 1 log sequence number 8299215891574
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:26  InnoDB: Error: page 20 log sequence number 8299215528487
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:26  InnoDB: Error: page 106216 log sequence number 8299348330353
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:26  InnoDB: Error: page 98305 log sequence number 8299434590706
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:26  InnoDB: Error: page 5 log sequence number 8299215789101
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:26  InnoDB: Error: page 114689 log sequence number 8299405235524
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:26  InnoDB: Error: page 6 log sequence number 8299215192961
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:26  InnoDB: Error: page 41756 log sequence number 8299307763762
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:26  InnoDB: Error: page 40961 log sequence number 8299348114573
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:26  InnoDB: Error: page 3 log sequence number 8299215891509
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Error: trying to access page number 1768711273 in space 995,
InnoDB: space name ./newsminer/pendingrobots.ibd,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 8192, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
110503 19:41:26  InnoDB: Assertion failure in thread 139775288796944 in file fil/fil0fil.c line 4686
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
110503 19:41:26 - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=33554432
read_buffer_size=2097152
max_used_connections=1
max_threads=500
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2086162 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = (nil) thread_stack 0x30000
/usr/local/mysql51/libexec/mysqld(my_print_stacktrace+0x29) [0x887c49]
/usr/local/mysql51/libexec/mysqld(handle_segfault+0x40d) [0x5abacd]
/lib/libpthread.so.0(+0xf8f0) [0x7f24b94668f0]
/lib/libc.so.6(gsignal+0x35) [0x7f24b8302a75]
/lib/libc.so.6(abort+0x180) [0x7f24b83065c0]
/usr/local/mysql51/libexec/mysqld() [0x813ddf]
/usr/local/mysql51/libexec/mysqld() [0x7f2aaf]
/usr/local/mysql51/libexec/mysqld() [0x7f2fd4]
/usr/local/mysql51/libexec/mysqld() [0x7eb11c]
/usr/local/mysql51/libexec/mysqld() [0x7d6b5b]
/usr/local/mysql51/libexec/mysqld() [0x795327]
/usr/local/mysql51/libexec/mysqld() [0x7939f3]
/usr/local/mysql51/libexec/mysqld() [0x794443]
/usr/local/mysql51/libexec/mysqld() [0x794da4]
/usr/local/mysql51/libexec/mysqld() [0x77fc6d]
/usr/local/mysql51/libexec/mysqld() [0x7af1ae]
/usr/local/mysql51/libexec/mysqld() [0x7a5bab]
/lib/libpthread.so.0(+0x69ca) [0x7f24b945d9ca]
/lib/libc.so.6(clone+0x6d) [0x7f24b83b56fd]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
110503 19:41:26 mysqld_safe Number of processes running now: 0
110503 19:41:26 mysqld_safe mysqld restarted
InnoDB: Warning: innodb_overwrite_relay_log_info is enabled. Updates in other storage engines may have problem with consistency.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3
110503 19:41:28  InnoDB: highest supported file format is Barracuda.
110503 19:41:29 Percona XtraDB (http://www.percona.com) 1.0.8-11.2 started; log sequence number 8298149359628
InnoDB: something wrong with relay-info.log. InnoDB will not overwrite it.
110503 19:41:29 [Note] Recovering after a crash using mysql-bin
110503 19:41:29 [Note] Starting crash recovery...
110503 19:41:29 [Note] Crash recovery finished.
110503 19:41:29 [Note] Event Scheduler: Loaded 0 events
110503 19:41:29 [Note] /usr/local/mysql51/libexec/mysqld: ready for connections.
Version: '5.1.47-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
110503 19:41:39  InnoDB: Error: page 4 log sequence number 8299215792744
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:39  InnoDB: Error: page 1 log sequence number 8299215891574
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:39  InnoDB: Error: page 20 log sequence number 8299215528487
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:39  InnoDB: Error: page 106216 log sequence number 8299348330353
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:39  InnoDB: Error: page 98305 log sequence number 8299434590706
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:39  InnoDB: Error: page 5 log sequence number 8299215789101
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:39  InnoDB: Error: page 114689 log sequence number 8299405235524
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:39  InnoDB: Error: page 6 log sequence number 8299215192961
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:39  InnoDB: Error: page 41756 log sequence number 8299307763762
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:39  InnoDB: Error: page 40961 log sequence number 8299348114573
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:39  InnoDB: Error: page 3 log sequence number 8299215891509
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Error: trying to access page number 1768711273 in space 995,
InnoDB: space name ./newsminer/pendingrobots.ibd,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 8192, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
110503 19:41:39  InnoDB: Assertion failure in thread 139628224427792 in file fil/fil0fil.c line 4686
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
110503 19:41:39 - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=33554432
read_buffer_size=2097152
max_used_connections=2
max_threads=500
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2086162 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = (nil) thread_stack 0x30000
/usr/local/mysql51/libexec/mysqld(my_print_stacktrace+0x29) [0x887c49]
/usr/local/mysql51/libexec/mysqld(handle_segfault+0x40d) [0x5abacd]
/lib/libpthread.so.0(+0xf8f0) [0x7f027b8e38f0]
/lib/libc.so.6(gsignal+0x35) [0x7f027a77fa75]
/lib/libc.so.6(abort+0x180) [0x7f027a7835c0]
/usr/local/mysql51/libexec/mysqld() [0x813ddf]
/usr/local/mysql51/libexec/mysqld() [0x7f2aaf]
/usr/local/mysql51/libexec/mysqld() [0x7f2fd4]
/usr/local/mysql51/libexec/mysqld() [0x7eb11c]
/usr/local/mysql51/libexec/mysqld() [0x7d6b5b]
/usr/local/mysql51/libexec/mysqld() [0x795327]
/usr/local/mysql51/libexec/mysqld() [0x7939f3]
/usr/local/mysql51/libexec/mysqld() [0x794443]
/usr/local/mysql51/libexec/mysqld() [0x794da4]
/usr/local/mysql51/libexec/mysqld() [0x77fc6d]
/usr/local/mysql51/libexec/mysqld() [0x7af1ae]
/usr/local/mysql51/libexec/mysqld() [0x7a5bab]
/lib/libpthread.so.0(+0x69ca) [0x7f027b8da9ca]
/lib/libc.so.6(clone+0x6d) [0x7f027a8326fd]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
110503 19:41:39 mysqld_safe Number of processes running now: 0
110503 19:41:39 mysqld_safe mysqld restarted
InnoDB: Warning: innodb_overwrite_relay_log_info is enabled. Updates in other storage engines may have problem with consistency.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3
110503 19:41:40  InnoDB: highest supported file format is Barracuda.
110503 19:41:41 Percona XtraDB (http://www.percona.com) 1.0.8-11.2 started; log sequence number 8298149359628
InnoDB: something wrong with relay-info.log. InnoDB will not overwrite it.
110503 19:41:41 [Note] Recovering after a crash using mysql-bin
110503 19:41:41 [Note] Starting crash recovery...
110503 19:41:41 [Note] Crash recovery finished.
110503 19:41:41 [Note] Event Scheduler: Loaded 0 events
110503 19:41:41 [Note] /usr/local/mysql51/libexec/mysqld: ready for connections.
Version: '5.1.47-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
110503 19:41:51  InnoDB: Error: page 4 log sequence number 8299215792744
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:51  InnoDB: Error: page 1 log sequence number 8299215891574
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:51  InnoDB: Error: page 20 log sequence number 8299215528487
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:51  InnoDB: Error: page 106216 log sequence number 8299348330353
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:51  InnoDB: Error: page 98305 log sequence number 8299434590706
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:51  InnoDB: Error: page 5 log sequence number 8299215789101
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:51  InnoDB: Error: page 114689 log sequence number 8299405235524
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:51  InnoDB: Error: page 6 log sequence number 8299215192961
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:51  InnoDB: Error: page 41756 log sequence number 8299307763762
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:51  InnoDB: Error: page 40961 log sequence number 8299348114573
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:41:51  InnoDB: Error: page 3 log sequence number 8299215891509
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Error: trying to access page number 1768711273 in space 995,
InnoDB: space name ./newsminer/pendingrobots.ibd,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 8192, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
110503 19:41:51  InnoDB: Assertion failure in thread 140030308439824 in file fil/fil0fil.c line 4686
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
110503 19:41:51 - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=33554432
read_buffer_size=2097152
max_used_connections=1
max_threads=500
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2086162 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = (nil) thread_stack 0x30000
/usr/local/mysql51/libexec/mysqld(my_print_stacktrace+0x29) [0x887c49]
/usr/local/mysql51/libexec/mysqld(handle_segfault+0x40d) [0x5abacd]
/lib/libpthread.so.0(+0xf8f0) [0x7f6019a158f0]
/lib/libc.so.6(gsignal+0x35) [0x7f60188b1a75]
/lib/libc.so.6(abort+0x180) [0x7f60188b55c0]
/usr/local/mysql51/libexec/mysqld() [0x813ddf]
/usr/local/mysql51/libexec/mysqld() [0x7f2aaf]
/usr/local/mysql51/libexec/mysqld() [0x7f2fd4]
/usr/local/mysql51/libexec/mysqld() [0x7eb11c]
/usr/local/mysql51/libexec/mysqld() [0x7d6b5b]
/usr/local/mysql51/libexec/mysqld() [0x795327]
/usr/local/mysql51/libexec/mysqld() [0x7939f3]
/usr/local/mysql51/libexec/mysqld() [0x794443]
/usr/local/mysql51/libexec/mysqld() [0x794da4]
/usr/local/mysql51/libexec/mysqld() [0x77fc6d]
/usr/local/mysql51/libexec/mysqld() [0x7af1ae]
/usr/local/mysql51/libexec/mysqld() [0x7a5bab]
/lib/libpthread.so.0(+0x69ca) [0x7f6019a0c9ca]
/lib/libc.so.6(clone+0x6d) [0x7f60189646fd]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
110503 19:41:52 mysqld_safe Number of processes running now: 0
110503 19:41:52 mysqld_safe mysqld restarted
InnoDB: Warning: innodb_overwrite_relay_log_info is enabled. Updates in other storage engines may have problem with consistency.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3
110503 19:41:53  InnoDB: highest supported file format is Barracuda.
110503 19:41:54 Percona XtraDB (http://www.percona.com) 1.0.8-11.2 started; log sequence number 8298149359628
InnoDB: something wrong with relay-info.log. InnoDB will not overwrite it.
110503 19:41:54 [Note] Recovering after a crash using mysql-bin
110503 19:41:54 [Note] Starting crash recovery...
110503 19:41:54 [Note] Crash recovery finished.
110503 19:41:54 [Note] Event Scheduler: Loaded 0 events
110503 19:41:54 [Note] /usr/local/mysql51/libexec/mysqld: ready for connections.
Version: '5.1.47-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
110503 19:42:04  InnoDB: Error: page 4 log sequence number 8299215792744
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:42:04  InnoDB: Error: page 1 log sequence number 8299215891574
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:42:04  InnoDB: Error: page 20 log sequence number 8299215528487
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:42:04  InnoDB: Error: page 106216 log sequence number 8299348330353
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:42:04  InnoDB: Error: page 98305 log sequence number 8299434590706
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:42:04  InnoDB: Error: page 5 log sequence number 8299215789101
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:42:04  InnoDB: Error: page 114689 log sequence number 8299405235524
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:42:04  InnoDB: Error: page 6 log sequence number 8299215192961
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:42:04  InnoDB: Error: page 41756 log sequence number 8299307763762
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:42:04  InnoDB: Error: page 40961 log sequence number 8299348114573
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:42:04  InnoDB: Error: page 3 log sequence number 8299215891509
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Error: trying to access page number 1768711273 in space 995,
InnoDB: space name ./newsminer/pendingrobots.ibd,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 8192, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
110503 19:42:04  InnoDB: Assertion failure in thread 139918789052176 in file fil/fil0fil.c line 4686
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
110503 19:42:04 - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=33554432
read_buffer_size=2097152
max_used_connections=2
max_threads=500
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2086162 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = (nil) thread_stack 0x30000
/usr/local/mysql51/libexec/mysqld(my_print_stacktrace+0x29) [0x887c49]
/usr/local/mysql51/libexec/mysqld(handle_segfault+0x40d) [0x5abacd]
/lib/libpthread.so.0(+0xf8f0) [0x7f46228e88f0]
/lib/libc.so.6(gsignal+0x35) [0x7f4621784a75]
/lib/libc.so.6(abort+0x180) [0x7f46217885c0]
/usr/local/mysql51/libexec/mysqld() [0x813ddf]
/usr/local/mysql51/libexec/mysqld() [0x7f2aaf]
/usr/local/mysql51/libexec/mysqld() [0x7f2fd4]
/usr/local/mysql51/libexec/mysqld() [0x7eb11c]
/usr/local/mysql51/libexec/mysqld() [0x7d6b5b]
/usr/local/mysql51/libexec/mysqld() [0x795327]
/usr/local/mysql51/libexec/mysqld() [0x7939f3]
/usr/local/mysql51/libexec/mysqld() [0x794443]
/usr/local/mysql51/libexec/mysqld() [0x794da4]
/usr/local/mysql51/libexec/mysqld() [0x77fc6d]
/usr/local/mysql51/libexec/mysqld() [0x7af1ae]
/usr/local/mysql51/libexec/mysqld() [0x7a5bab]
/lib/libpthread.so.0(+0x69ca) [0x7f46228df9ca]
/lib/libc.so.6(clone+0x6d) [0x7f46218376fd]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
110503 19:42:04 mysqld_safe Number of processes running now: 0
110503 19:42:04 mysqld_safe mysqld restarted
InnoDB: Warning: innodb_overwrite_relay_log_info is enabled. Updates in other storage engines may have problem with consistency.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3
110503 19:42:05  InnoDB: highest supported file format is Barracuda.
110503 19:42:06 Percona XtraDB (http://www.percona.com) 1.0.8-11.2 started; log sequence number 8298149359628
InnoDB: something wrong with relay-info.log. InnoDB will not overwrite it.
110503 19:42:06 [Note] Recovering after a crash using mysql-bin
110503 19:42:06 [Note] Starting crash recovery...
110503 19:42:06 [Note] Crash recovery finished.
110503 19:42:07 [Note] Event Scheduler: Loaded 0 events
110503 19:42:07 [Note] /usr/local/mysql51/libexec/mysqld: ready for connections.
Version: '5.1.47-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
110503 19:42:17  InnoDB: Error: page 4 log sequence number 8299215792744
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:42:17  InnoDB: Error: page 1 log sequence number 8299215891574
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:42:17  InnoDB: Error: page 20 log sequence number 8299215528487
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:42:17  InnoDB: Error: page 106216 log sequence number 8299348330353
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:42:17  InnoDB: Error: page 98305 log sequence number 8299434590706
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:42:17  InnoDB: Error: page 5 log sequence number 8299215789101
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:42:17  InnoDB: Error: page 114689 log sequence number 8299405235524
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:42:17  InnoDB: Error: page 6 log sequence number 8299215192961
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:42:17  InnoDB: Error: page 41756 log sequence number 8299307763762
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:42:17  InnoDB: Error: page 40961 log sequence number 8299348114573
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:42:17  InnoDB: Error: page 3 log sequence number 8299215891509
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Error: trying to access page number 1768711273 in space 995,
InnoDB: space name ./newsminer/pendingrobots.ibd,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 8192, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
110503 19:42:17  InnoDB: Assertion failure in thread 139763849455376 in file fil/fil0fil.c line 4686
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
110503 19:42:17 - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=33554432
read_buffer_size=2097152
max_used_connections=2
max_threads=500
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2086162 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = (nil) thread_stack 0x30000
/usr/local/mysql51/libexec/mysqld(my_print_stacktrace+0x29) [0x887c49]
/usr/local/mysql51/libexec/mysqld(handle_segfault+0x40d) [0x5abacd]
/lib/libpthread.so.0(+0xf8f0) [0x7f220f6fe8f0]
/lib/libc.so.6(gsignal+0x35) [0x7f220e59aa75]
/lib/libc.so.6(abort+0x180) [0x7f220e59e5c0]
/usr/local/mysql51/libexec/mysqld() [0x813ddf]
/usr/local/mysql51/libexec/mysqld() [0x7f2aaf]
/usr/local/mysql51/libexec/mysqld() [0x7f2fd4]
/usr/local/mysql51/libexec/mysqld() [0x7eb11c]
/usr/local/mysql51/libexec/mysqld() [0x7d6b5b]
/usr/local/mysql51/libexec/mysqld() [0x795327]
/usr/local/mysql51/libexec/mysqld() [0x7939f3]
/usr/local/mysql51/libexec/mysqld() [0x794443]
/usr/local/mysql51/libexec/mysqld() [0x794da4]
/usr/local/mysql51/libexec/mysqld() [0x77fc6d]
/usr/local/mysql51/libexec/mysqld() [0x7af1ae]
/usr/local/mysql51/libexec/mysqld() [0x7a5bab]
/lib/libpthread.so.0(+0x69ca) [0x7f220f6f59ca]
/lib/libc.so.6(clone+0x6d) [0x7f220e64d6fd]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
110503 19:42:17 mysqld_safe Number of processes running now: 0
110503 19:42:17 mysqld_safe mysqld restarted
InnoDB: Warning: innodb_overwrite_relay_log_info is enabled. Updates in other storage engines may have problem with consistency.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3
110503 19:42:18  InnoDB: highest supported file format is Barracuda.
110503 19:42:19 Percona XtraDB (http://www.percona.com) 1.0.8-11.2 started; log sequence number 8298149359628
InnoDB: something wrong with relay-info.log. InnoDB will not overwrite it.
110503 19:42:19 [Note] Recovering after a crash using mysql-bin
110503 19:42:19 [Note] Starting crash recovery...
110503 19:42:19 [Note] Crash recovery finished.
110503 19:42:19 [Note] Event Scheduler: Loaded 0 events
110503 19:42:19 [Note] /usr/local/mysql51/libexec/mysqld: ready for connections.
Version: '5.1.47-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
110503 19:42:29  InnoDB: Error: page 4 log sequence number 8299215792744
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:42:29  InnoDB: Error: page 1 log sequence number 8299215891574
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:42:29  InnoDB: Error: page 20 log sequence number 8299215528487
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:42:29  InnoDB: Error: page 106216 log sequence number 8299348330353
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:42:29  InnoDB: Error: page 98305 log sequence number 8299434590706
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:42:29  InnoDB: Error: page 5 log sequence number 8299215789101
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:42:29  InnoDB: Error: page 114689 log sequence number 8299405235524
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:42:29  InnoDB: Error: page 6 log sequence number 8299215192961
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:42:29  InnoDB: Error: page 41756 log sequence number 8299307763762
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:42:29  InnoDB: Error: page 40961 log sequence number 8299348114573
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110503 19:42:29  InnoDB: Error: page 3 log sequence number 8299215891509
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Error: trying to access page number 1768711273 in space 995,
InnoDB: space name ./newsminer/pendingrobots.ibd,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 8192, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
110503 19:42:29  InnoDB: Assertion failure in thread 139738481129232 in file fil/fil0fil.c line 4686
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
110503 19:42:29 - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=33554432
read_buffer_size=2097152
max_used_connections=2
max_threads=500
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2086162 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = (nil) thread_stack 0x30000
/usr/local/mysql51/libexec/mysqld(my_print_stacktrace+0x29) [0x887c49]
/usr/local/mysql51/libexec/mysqld(handle_segfault+0x40d) [0x5abacd]
/lib/libpthread.so.0(+0xf8f0) [0x7f1c275df8f0]
/lib/libc.so.6(gsignal+0x35) [0x7f1c2647ba75]
/lib/libc.so.6(abort+0x180) [0x7f1c2647f5c0]
/usr/local/mysql51/libexec/mysqld() [0x813ddf]
/usr/local/mysql51/libexec/mysqld() [0x7f2aaf]
/usr/local/mysql51/libexec/mysqld() [0x7f2fd4]
/usr/local/mysql51/libexec/mysqld() [0x7eb11c]
/usr/local/mysql51/libexec/mysqld() [0x7d6b5b]
/usr/local/mysql51/libexec/mysqld() [0x795327]
/usr/local/mysql51/libexec/mysqld() [0x7939f3]
/usr/local/mysql51/libexec/mysqld() [0x794443]
/usr/local/mysql51/libexec/mysqld() [0x794da4]
/usr/local/mysql51/libexec/mysqld() [0x77fc6d]
/usr/local/mysql51/libexec/mysqld() [0x7af1ae]
/usr/local/mysql51/libexec/mysqld() [0x7a5bab]
/lib/libpthread.so.0(+0x69ca) [0x7f1c275d69ca]
/lib/libc.so.6(clone+0x6d) [0x7f1c2652e6fd]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.