Abdulla, ----- Original Message ----- From: ""Paizulaev Abdula"" <[EMAIL PROTECTED]> Newsgroups: mailing.database.myodbc Sent: Monday, April 05, 2004 7:43 AM Subject: mysqld crash, got following
> InnoDB: Error: record field 3 len 4294967207 > Heap no too big 5888 93 > Error in page 117145 in index PRIMARY > Record has 654 fields, should have 24 the table radacct is corrupt. And because the corruption is in the PRIMARY index, you may not be able to dump all the rows. http://www.innodb.com/ibman.php#Forcing.recovery innodb_force_recovery=4 may help in dumping most of the table. Then DROP + reimport the dump. > InnoDB: record RECORD: info bits 0 0: > 040405 8:36:56 InnoDB: Assertion failure in thread 9226 in file > ../include/page0page.ic line 482 > InnoDB: We intentionally generate a memory trap. > InnoDB: Send a detailed bug report to [EMAIL PROTECTED] > 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=8388600 > record_buffer=131072 > sort_buffer=2097144 > max_used_connections=0 > max_connections=16 > threads_connected=1 > It is possible that mysqld could use up to > key_buffer_size + (record_buffer + sort_buffer)*max_connections = 43007 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... > Stack range sanity check OK, backtrace follows: > 0x80c9d62 > 0x40027f75 > 0x819d1bc > 0x819db86 > 0x81a3168 > 0x8171a83 > 0x811a431 > 0x811fcb4 > 0x812299a > 0x80d1793 > 0x80d390f > 0x80cfc3e > 0x80cf0e4 > Stack trace seems successful - bottom reached > Please read http://www.mysql.com/doc/U/s/Using_stack_trace.html and follow > instructions on how to resolve the stack trace. Resolved > stack trace is much more helpful in diagnosing the problem, so please do > resolve it > Trying to get some variables. > Some pointers may be invalid and cause the dump to abort... > thd->query at 0x85eb3a8 = CHECK TABLE `radacct` EXTENDED > thd->thread_id=1 > > Successfully dumped variables, if you ran with --log, take a look at the > details of what thread 1 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 > > Number of processes running now: 0 > 040405 08:36:56 mysqld restarted > 040405 8:36:58 InnoDB: Started > > --- > Abdulla Paizulaev, 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 Register now for the 2004 MySQL Users Conference! http://www.mysql.com/events/uc2004/index.html -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
