Description:
I can´t start mysqld any more, although i haven´t made any updates on the system or on mysql.
The output of the logfile is:
--------------------------------------------
121112 2:10:23 InnoDB: Page checksum 2744661067, prior-to-4.0.14-form checksum 2357256288
InnoDB: stored checksum 2379129211, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 0 97642795, low 4 bytes of lsn at page end 97642795
InnoDB: Page number (if stored to page already) 1267,
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 0 242
121112 2:10:23InnoDB: Assertion failure in thread 1132276032 in file page0page.c line 132
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.0/en/forcing-recovery.html
InnoDB: about forcing recovery.
121112 2:10:23 - 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=0
read_buffer_size=131072
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 217599 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=(nil)
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...
frame pointer is NULL, did you compile with
-fomit-frame-pointer? Aborting backtrace!
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.
121112 02:10:23 mysqld ended
------------------------------------
This could be the heart of the problem:
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace.
How to repeat:
I really don´t know.
Suggested fix:
I really don´t know.
