Dave,
please post the first errors in the .err log. I want to know what the original problem was. The error below probably comes from that you have set
innodb_force_recovery=SRV_FORCE_NO_LOG_REDO
Note that Red Hat kernels 2.4.18 are suspected to cause file corruption easily.
Best regards,
Heikki Tuuri
Innobase Oy
Foreign keys, transactions, and row level locking for MySQL
InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM tables
http://www.innodb.com/order.php
Order MySQL technical support from https://order.mysql.com/
----- Original Message ----- From: "Dave Dunnagan" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Sunday, December 26, 2004 6:01 AM
Subject: InnoDB Assertion failure
Greetings.
MySQL 4.0.20 has run flawlessly here for 7 months on a Linux 2.4.18-14 (Redhat 8) box serving 5 small databases for PHP websites. But something appears to have happened to my installation on Dec 23 that now prevents MySQL from starting. I've reviewed the instructions about forcing InnoDB recovery and MySQL crash resolution, but no luck so far. Any help would be deeply appreciated! The following is an extract from the .err file after an attempted startup:
041225 22:14:48 mysqld started
041225 22:14:48 Warning: Asked for 196608 thread stack, but got 126976
InnoDB: The user has set SRV_FORCE_NO_LOG_REDO on
InnoDB: Skipping log redo
041225 22:14:49InnoDB: Assertion failure in thread 4096 in file
fil0fil.c line 1193
InnoDB: Failing assertion: space
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. See section 6.1 of
InnoDB: http://www.innodb.com/ibman.php about forcing recovery.
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=16777216 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 = 80383 K bytes of memory Hope that's ok; if not, decrease some variables in the equation.
thd=0x8400a20 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=0xbfffeea8, stack_bottom=0x76fa70f0, thread_stack=126976, aborting backtrace. Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x762f5be0 is invalid pointer thd->thread_id=1768697714 The manual page at http://www.mysql.com/doc/en/Crashing.html contains information that should help you find out what is causing the crash. 041225 22:14:49 mysqld ended
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
