Adam, in your earlier message you quoted 3 log files, but below in the printout it says 2 log files. Best to do
SHOW VARIABLES; and check from the current directory innodb_log_group_home_dir how many ib_logfiles there really are. " 030107 06:42:58 mysqld started /usr/local/mysql/bin/mysqld: unrecognized option `--innodb_log_files_in_group=3' " > /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) If I try the wrong syntax, I get: heikki@hundin:~/mysql-max-3.23.53a-pc-linux-gnu-i686/bin> mysqld mysqld: unrecognized option `--innodb_log_files_in_group=3' mysqld Ver 3.23.53a-max for pc-linux-gnu on i686 I resolved the stack dump: 0x806bdc5 handle_segfault__Fi + 425 0x8247a78 pthread_sighandler + 184 0x815450c btr_search_info_update_slow + 1072 0x813fe5e btr_cur_search_to_nth_level + 3178 0x811586b row_sel_get_clust_rec_for_mysql + 99 0x8118704 row_search_for_mysql + 6836 0x80b6802 general_fetch__11ha_innobasePcUiUi + 322 0x80b68d0 index_next_same__11ha_innobasePcPCcUi + 40 0x809142d join_read_next__FP14st_read_record + 53 0x8090b89 sub_select__FP4JOINP13st_join_tableb + 337 0x8090843 do_select__FP4JOINPt4List1Z4ItemP8st_tableP9Procedure + 407 0x8089688 mysql_select__FP3THDP13st_table_listRt4List1Z4ItemP4ItemP8st_orderT4T3 T4UiP13select_result + 5592 0x8072320 mysql_execute_command__Fv + 812 0x80755a8 mysql_parse__FP3THDPcUi + 72 0x80714c4 do_command__FP3THD + 1316 0x8070997 handle_one_connection__FPv + 655 It is possible that the bug is one which is fixed in the upcoming 3.23.55 and in 4.0.8. It could also be memory corruption. What is your Linux kernel version? It is best that you run CHECK TABLE on some tables. " MySQL/InnoDB-3.23.55, February x, 2003 ... a.. Fixed a bug: an assertion in btr0sea.c, in function btr_search_info_update_slow could theoretically fail in a race of 3 threads. " Regards, Heikki Innobase Oy sql query Subject: bug report From: Adam Gillespie Date: Tue, 7 Jan 2003 09:29:59 -0800 ---------------------------------------------------------------------------- ---- 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
