Our db server crashed and this was in the log. One strange thing was that when I went to restart, the error log gave me this line: /usr/local/mysql/bin/mysqld: unrecognized option `--innodb_log_files_in_group=2' We have not touched /etc/my.cnf and have restarted the server many times. I had to change it to: set-variable=innodb_log_files_in_group=2 to get it to restart (a suggestion by Heikki Tuuri)
030107 4:05:57 InnoDB: Assertion failure in thread 11497484 in file btr0sea.c line 456 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 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=134213632 record_buffer=2093056 sort_buffer=2097144 max_used_connections=65 max_connections=300 threads_connected=2 It is possible that mysqld could use up to key_buffer_size + (record_buffer + sort_buffer)*max_connections = 1358665 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: 0x806bdc5 0x8247a78 0x815450c 0x813fe5e 0x811586b 0x8118704 0x80b6802 0x80b68d0 0x809142d 0x8090b89 0x8090843 0x8089688 0x8072320 0x80755a8 0x80714c4 0x8070997 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. Res olved 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 0xa9935960 is invalid pointer thd->thread_id=4307634 Successfully dumped variables, if you ran with --log, take a look at the details of what thread 4307634 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 030107 04:05:58 mysqld restarted /usr/local/mysql/bin/mysqld: unrecognized option `--innodb_log_files_in_group=2' /usr/local/mysql/bin/mysqld Ver 3.23.53a-max for pc-linux-gnu on i686 Copyright (C) 2000 MySQL AB, by Monty and others This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to modify and redistribute it under the GPL license Starts the MySQL server Usage: /usr/local/mysql/bin/mysqld [OPTIONS] --ansi Use ANSI SQL syntax instead of MySQL syntax -b, --basedir=path Path to installation directory. All paths are usually resolved relative to this... the rest of the options follow --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php