Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- key_buffer_size=16777216
- read_buffer_size=131072
- 141005 15:13:56max_used_connections=0
- max_threads=151
- InnoDB: 5.5.38 started; log sequence number 2455246113
- thread_count=0
- connection_count=0
- It is possible that mysqld could use up to
- key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346700 K bytes of memory
- Hope that's ok; if not, decrease some variables in the equation.
- Thread pointer: 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 = 0 thread_stack 0x30000
- 141005 15:13:56 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
- 141005 15:13:56 [Note] - '127.0.0.1' resolves to '127.0.0.1';
- 141005 15:13:56 [Note] Server socket created on IP: '127.0.0.1'.
- /usr/sbin/mysqld(my_print_stacktrace+0x20)[0x7fa26639ef20]
- /usr/sbin/mysqld(handle_fatal_signal+0x3d5)[0x7fa2662898d5]
- /lib/x86_64-linux-gnu/libpthread.so.0(+0x10340)[0x7fa264ff8340]
- /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x39)[0x7fa264646bb9]
- /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7fa264649fc8]
- /usr/sbin/mysqld(+0x2732d0)[0x7fa2661232d0]
- /usr/sbin/mysqld(+0x58b836)[0x7fa26643b836]
- /usr/sbin/mysqld(+0x58bbcd)[0x7fa26643bbcd]
- /usr/sbin/mysqld(+0x64d16f)[0x7fa2664fd16f]
- /usr/sbin/mysqld(+0x643ab5)[0x7fa2664f3ab5]
- /usr/sbin/mysqld(+0x58da45)[0x7fa26643da45]
- /usr/sbin/mysqld(+0x57f65c)[0x7fa26642f65c]
- /usr/sbin/mysqld(+0x583733)[0x7fa266433733]
- /lib/x86_64-linux-gnu/libpthread.so.0(+0x8182)[0x7fa264ff0182]
- /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fa26470afbd]
- 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.
- 141005 15:13:57 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
- 141005 15:13:57 [Note] Plugin 'FEDERATED' is disabled.
- 141005 15:13:57 InnoDB: The InnoDB memory heap is disabled
- 141005 15:13:57 InnoDB: Mutexes and rw_locks use GCC atomic builtins
- 141005 15:13:57 InnoDB: Compressed tables use zlib 1.2.8
- 141005 15:13:57 InnoDB: Using Linux native AIO
- 141005 15:13:57 InnoDB: Initializing buffer pool, size = 128.0M
- 141005 15:13:57 InnoDB: Completed initialization of buffer pool
- 141005 15:13:57 InnoDB: highest supported file format is Barracuda.
- 141005 15:13:57 InnoDB: Error: page 5 log sequence number 2455516206
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 51 log sequence number 2455632585
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 56 log sequence number 2455644510
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 2560 log sequence number 2455258974
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 2561 log sequence number 2455270772
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 2600 log sequence number 2455282596
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 2619 log sequence number 2455296303
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 2587 log sequence number 2455321908
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 2603 log sequence number 2455336696
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 1590 log sequence number 2455362122
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 2563 log sequence number 2455373946
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 2107 log sequence number 2455411915
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 2607 log sequence number 2455425623
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 2608 log sequence number 2455425851
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 2590 log sequence number 2455426095
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 256 log sequence number 2455426323
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 1645 log sequence number 2455426323
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 257 log sequence number 2455438973
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 2545 log sequence number 2455438973
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 260 log sequence number 2455450797
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 261 log sequence number 2455464261
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 2546 log sequence number 2455464261
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 263 log sequence number 2455464505
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 1594 log sequence number 2455464505
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 268 log sequence number 2455464733
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 2593 log sequence number 2455464733
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 271 log sequence number 2455465105
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 2623 log sequence number 2455465105
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 274 log sequence number 2455477855
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 275 log sequence number 2455478083
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 2509 log sequence number 2455478083
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 276 log sequence number 2455479059
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 2547 log sequence number 2455479059
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 278 log sequence number 2455490875
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 1738 log sequence number 2455490875
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 280 log sequence number 2455503447
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 2548 log sequence number 2455503447
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 281 log sequence number 2455516196
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 284 log sequence number 2455529799
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 2549 log sequence number 2455529799
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 285 log sequence number 2455541596
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 287 log sequence number 2455553419
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 2580 log sequence number 2455553419
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 288 log sequence number 2455566275
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 289 log sequence number 2455579006
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 290 log sequence number 2455592486
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 2551 log sequence number 2455592486
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 291 log sequence number 2455592713
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 2514 log sequence number 2455592713
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 292 log sequence number 2455606177
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 2552 log sequence number 2455606177
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 295 log sequence number 2455619787
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 2553 log sequence number 2455619787
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 296 log sequence number 2455620892
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 141005 15:13:57 InnoDB: Error: page 2554 log sequence number 2455620892
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- InnoDB: 3 transaction(s) which must be rolled back or cleaned up
- InnoDB: in total 3 row operations to undo
- InnoDB: Trx id counter is F1F00
- 141005 15:13:57 InnoDB: Error: page 0 log sequence number 2455620555
- InnoDB: is in the future! Current system log sequence number 2455246113.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- InnoDB: Cleaning up trx with id F1CC9
- InnoDB: Cleaning up trx with id F1CBC
- InnoDB: Cleaning up trx with id F1CAC
- 141005 15:13:57 InnoDB: Waiting for the background threads to start
- 141005 15:13:58 InnoDB: 5.5.38 started; log sequence number 2455246113
- 141005 15:13:58 InnoDB: Assertion failure in thread 140442187269888 in file fut0lst.ic line 83
- InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
- 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.5/en/forcing-innodb-recovery.html
- InnoDB: about forcing recovery.
- 12:13:58 UTC - 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.
Advertisement
Add Comment
Please, Sign In to add comment