Hello,
after a server-recovery to the saved data from yesterday MySQL won't start. starting mysqld shows the following errors. Can anyone help me to repair this database? I think that the automaztically backup saved the mysql-files during write-operations so that some tables are corrupted. :
InnoDB: End of page dump
140627 20:35:53 InnoDB: Page checksum 756557882, prior-to-4.0.14-form checksum 3430747706
InnoDB: stored checksum 1768400972, prior-to-4.0.14-form stored checksum 3430747706
InnoDB: Page lsn 25 4180489299, low 4 bytes of lsn at page end 4180489299
InnoDB: Page number (if stored to page already) 49170,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be an index page where index id is 2116
InnoDB: Also the page in the doublewrite buffer is corrupt.
InnoDB: Cannot continue operation.
InnoDB: You can try to recover the database with the my.cnf
InnoDB: option:
InnoDB: innodb_force_recovery=6
140627 20:35:53 InnoDB: Assertion failure in thread 3064682240 in file trx0sys.c line 606
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.
18:35:53 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.
key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=151
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 = 346075 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
mysqld(my_print_stacktrace+0x33)[0xb72d0b83]
mysqld(handle_fatal_signal+0x484)[0xb717cf14]
[0xb6e30500]
mysqld(+0x5ee6e3)[0xb74416e3]
mysqld(+0x5f37e2)[0xb74467e2]
mysqld(+0x541571)[0xb7394571]
mysqld(+0x505682)[0xb7358682]
mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x4e)[0xb717f73e]
mysqld(+0x1fe592)[0xb7051592]
mysqld(_Z11plugin_initPiPPci+0xbc3)[0xb7054f63]
mysqld(+0x166f4a)[0xb6fb9f4a]
mysqld(_Z11mysqld_mainiPPc+0x6d1)[0xb6fbdd21]
mysqld(main+0x27)[0xb6fb3167]
/lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf3)[0xb6aea4d3]
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.
Thanks,
Siegbert
after a server-recovery to the saved data from yesterday MySQL won't start. starting mysqld shows the following errors. Can anyone help me to repair this database? I think that the automaztically backup saved the mysql-files during write-operations so that some tables are corrupted. :
InnoDB: End of page dump
140627 20:35:53 InnoDB: Page checksum 756557882, prior-to-4.0.14-form checksum 3430747706
InnoDB: stored checksum 1768400972, prior-to-4.0.14-form stored checksum 3430747706
InnoDB: Page lsn 25 4180489299, low 4 bytes of lsn at page end 4180489299
InnoDB: Page number (if stored to page already) 49170,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be an index page where index id is 2116
InnoDB: Also the page in the doublewrite buffer is corrupt.
InnoDB: Cannot continue operation.
InnoDB: You can try to recover the database with the my.cnf
InnoDB: option:
InnoDB: innodb_force_recovery=6
140627 20:35:53 InnoDB: Assertion failure in thread 3064682240 in file trx0sys.c line 606
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.
18:35:53 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.
key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=151
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 = 346075 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
mysqld(my_print_stacktrace+0x33)[0xb72d0b83]
mysqld(handle_fatal_signal+0x484)[0xb717cf14]
[0xb6e30500]
mysqld(+0x5ee6e3)[0xb74416e3]
mysqld(+0x5f37e2)[0xb74467e2]
mysqld(+0x541571)[0xb7394571]
mysqld(+0x505682)[0xb7358682]
mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x4e)[0xb717f73e]
mysqld(+0x1fe592)[0xb7051592]
mysqld(_Z11plugin_initPiPPci+0xbc3)[0xb7054f63]
mysqld(+0x166f4a)[0xb6fb9f4a]
mysqld(_Z11mysqld_mainiPPc+0x6d1)[0xb6fbdd21]
mysqld(main+0x27)[0xb6fb3167]
/lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf3)[0xb6aea4d3]
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.
Thanks,
Siegbert