j, how you have set
innodb_thread_concurrency and innodb_log_file_size in my.cnf? I was able to repeat the assertion failure by setting the log file size to only 8 MB, and setting concurrency to 500. I changed now InnoDB so that it no longer asserts, but calls exit(1). It prints the following instructions if log files are too small for the concurrency: if (!success) { fprintf(stderr, "InnoDB: Error: ib_logfiles are too small for innodb_thread_concurrency %lu.\n" "InnoDB: The combined size of ib_logfiles should be bigger than\n" "InnoDB: 200 kB * innodb_thread_concurrency.\n" "InnoDB: To get mysqld to start up, set innodb_thread_concurrency in my.cnf\n" "InnoDB: to a lower value, for example, to 8. After an ERROR-FREE shutdown\n" "InnoDB: of mysqld you can adjust the size of ib_logfiles, as explained in\n" "InnoDB: section 5 of http://www.innodb.com/ibman.php", (ulong)srv_thread_concurrency); fprintf(stderr, "InnoDB: Cannot continue operation. Calling exit(1).\n"); exit(1); } Merry Christmas! Heikki Tuuri Innobase Oy http://www.innodb.com Foreign keys, transactions, and row level locking for MySQL InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM tables Order MySQL technical support from https://order.mysql.com/ ----- Original Message ----- From: ""j.random.programmer"" <[EMAIL PROTECTED]> Newsgroups: mailing.database.myodbc Sent: Tuesday, December 23, 2003 5:49 AM Subject: BUG: Innodb, Assertion failure in file log0log.c with 4.0.!7 > There is a MySQl/Innodb bug with Mysql-Max 4.0.17 > on mac osx 10.3 panther. A google search showed > a similar problem with another platform (I think > it was windows). > > I am running 4.0.14 without any problems. After > upgrading to 4.0.17, copying the data directory > from 4.0.14 to 4.0.17 and then starting mysqld > I get: > > --------------------------------------- > 031222 22:05:51 mysqld started > InnoDB: Error: log file group too small for > innodb_thread_concurrency > 031222 22:05:51 InnoDB: Assertion failure in thread > 2684396012 in file log0log.c line 856 > InnoDB: Failing assertion: log_calc_max_ages() > InnoDB: We intentionally generate a memory trap. > InnoDB: Send a detailed bug report to > [EMAIL PROTECTED] > mysqld got signal 10; > 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. > --------------------------------------------- > > Reverting back to 4.0.14 works fine and I > get no error messages. > > Best regards, > > --j > > > __________________________________ > Do you Yahoo!? > New Yahoo! Photos - easier uploading and sharing. > http://photos.yahoo.com/ > > -- > 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]