Hello.
I don't see any attempts from InnoDB to recover the data, so it is crashing before the recovering. To save your data, if you're unable to get tables with mysqldump, this might be helpful: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html > MySQL 3.2.3 installed in our server suddenly started giving problem after restarting the server m/c. This version '3.2.3' looks too old for me. I strongly recommend you to upgrade to the latest release. Arunoday Chatterjee wrote: > MySQL 3.2.3 installed in our server suddenly started giving problem after > restarting the server m/c. > /etc/init.d/mysqld status sys, > > mysqld dead but subsys locked > > Checked the log file and found that there is some Assertion failure for > InnoDB, can you pls. provide a possible solution for this. > > Some pointers may be invalid and cause the dump to abort... > thd->query at 0x3ac6fc20 is invalid pointer > thd->thread_id=0 > > Successfully dumped variables, if you ran with --log, take a look at the > details of what thread 0 did to cause the crash. In some cases of really > bad corruption, the values shown above may be invalid > > The manual page at http://www.mysql.com/doc/C/r/Crashing.html contains > information that should help you find out what is causing the crash > 051109 00:41:00 mysqld ended > > 051109 09:38:56 mysqld started > 051109 9:39:00 InnoDB: Assertion failure in thread 8192 in file os0file.c > line 1044 > InnoDB: We intentionally generate a memory trap. > InnoDB: Send a detailed bug report to mysql@lists.mysql.com > 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 agaist 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=8388600 > record_buffer=131072 > sort_buffer=2097144 > max_used_connections=0 > max_connections=250 > threads_connected=0 > It is possible that mysqld could use up to > key_buffer_size + (record_buffer + sort_buffer)*max_connections = 552190 K > bytes of memory > Hope that's ok, if not, decrease some variables in the equation > > 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... > Bogus stack limit or frame pointer, fp=0xbfffd488, stack_bottom=0x3bdbc910, > thread_stack=65536, aborting backtrace. > Trying to get some variables. > Some pointers may be invalid and cause the dump to abort... > thd->query at 0x3ac6fc20 is invalid pointer > thd->thread_id=0 > > Successfully dumped variables, if you ran with --log, take a look at the > details of what thread 0 did to cause the crash. In some cases of really > bad corruption, the values shown above may be invalid > > The manual page at http://www.mysql.com/doc/C/r/Crashing.html contains > information that should help you find out what is causing the crash > 051109 09:39:08 mysqld ended > > 051109 10:06:15 mysqld started > 051109 10:06:15 InnoDB: Assertion failure in thread 8192 in file os0file.c > line 1044 > InnoDB: We intentionally generate a memory trap. > InnoDB: Send a detailed bug report to mysql@lists.mysql.com > 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 agaist is corrupt, improperly built, > or misconfigured. This error can also be caused by malfunctioning hardware. > We will try our best to scrape up som051109 10:06:15 mysqld ended > > 051109 10:08:18 mysqld started > 051109 10:08:18 InnoDB: Assertion failure in thread 8192 in file os0file.c > line 1044 > InnoDB: We intentionally generate a memory trap. > InnoDB: Send a detailed bug report to mysql@lists.mysql.com > 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 agaist 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=8388600 > record_buffer=131072 > sort_buffer=2097144 > max_used_connections=0 > max_connections=250 > threads_connected=0 > > 051109 10:08:18 mysqld started > 051109 10:08:18 InnoDB: Assertion failure in thread 8192 in file os0file.c > line 1044 > InnoDB: We intentionally generate a memory trap. > InnoDB: Send a detailed bug report to mysql@lists.mysql.com > 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 agaist 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=8388600 > record_buffer=131072 > sort_buffer=2097144 > max_used_connections=0 > max_connections=250 > threads_connected=0 > It is possible that mysqld could use up to > key_buffer_size + (record_buffer + sort_buffer)*max_connections = 552190 K > bytes of memory > "/var/log/mysqld.log" 220L, 10000C > -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
