Hi people,
Since an couple of hours im the error that my mysql server does not want to start.
Because it seems the last backup's are not completed/ not done.
Im really should rebuild or reinstall mysql with the current databases!
Im getting this message in my log!
It is on a system running debian!
If any one can help me! Thank you
Since an couple of hours im the error that my mysql server does not want to start.
Because it seems the last backup's are not completed/ not done.
Im really should rebuild or reinstall mysql with the current databases!
Im getting this message in my log!
InnoDB: Log scan progressed past the checkpoint lsn 0 191420428
100930 22:17:31 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 0 191420642
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 1 row operations to undo
InnoDB: Trx id counter is 0 14812416
100930 22:17:31 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
InnoDB: Starting in background the rollback of uncommitted transactions
100930 22:17:32 InnoDB: Rolling back trx with id 0 14812050, 1 rows to undo
InnoDB: Error: trying to access page number 69841 in space 0,
InnoDB: space name ./ibdata1,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 16384, 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.
100930 22:17:32 InnoDB: Assertion failure in thread 3017157520 in file fil/fil0fil.c line 4073
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.
100930 22:17:32 - 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=8384512
read_buffer_size=131072
max_used_connections=0
max_threads=151
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 337724 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/mysql/bin/mysqld(my_print_stacktrace+0x21)[0x84d6981]
/usr/local/mysql/bin/mysqld(handle_segfault+0x381)[0x8200291]
[0xb77ac400]
/lib/i686/cmov/libc.so.6(abort+0x188)[0xb75e8018]
/usr/local/mysql/bin/mysqld(fil_io+0x36c)[0x83d1bfc]
/usr/local/mysql/bin/mysqld[0x83bb4bb]
/usr/local/mysql/bin/mysqld(buf_read_page+0x1ec)[0x83bbe3c]
/usr/local/mysql/bin/mysqld(buf_page_get_gen+0x2c5)[0x83b5cf5]
/usr/local/mysql/bin/mysqld(flst_insert_before+0x296)[0x83df336]
/usr/local/mysql/bin/mysqld(flst_add_first+0x122)[0x83e0602]
/usr/local/mysql/bin/mysqld(trx_purge_add_update_undo_to_history+0x105)[0x8440ed5]
/usr/local/mysql/bin/mysqld(trx_undo_update_cleanup+0x2e)[0x845111e]
/usr/local/mysql/bin/mysqld(trx_commit_off_kernel+0x1c7)[0x844f877]
/usr/local/mysql/bin/mysqld(trx_finish_rollback_off_kernel+0x43)[0x8447dc3]
/usr/local/mysql/bin/mysqld[0x84132c3]
/usr/local/mysql/bin/mysqld(que_run_threads+0xdf)[0x841349f]
/usr/local/mysql/bin/mysqld(trx_rollback_or_clean_all_without_sess+0x37c)[0x8448f9c]
/lib/i686/cmov/libpthread.so.0[0xb77924c0]
/lib/i686/cmov/libc.so.6(clone+0x5e)[0xb769b84e]
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.
100930 22:17:32 mysqld_safe mysqld from pid file /usr/local/mysql/data/62.pid ended
It is on a system running debian!
If any one can help me! Thank you