Richard, 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.
Also note that you should make sort buffer and record buffer smaller, say 512k. mysqld may be hogging too much memory. record_buffer=2093056 sort_buffer=2097144 max_used_connections=385 max_connections=2000 threads_connected=382 It is possible that mysqld could use up to key_buffer_size + (record_buffer + sort_buffer)*max_connections = 3997872 K Best regards, Heikki Tuuri Innobase Oy http://www.innodb.com Transactions, foreign keys, and a hot backup tool for MySQL Order MySQL technical support from https://order.mysql.com/ .................. Subject: RH 8.0 InnoDB: Assertion failure in thread 122911 in file mem0pool.c line 477 From: Richard F. Rebel Date: 04 Jun 2003 11:43:49 -0400 I have reported this before, but MySQL-Max-3.23.56-1 (official rpm's) is repeatedly crashing. Often when executing queries on an InnoDB table with about 1300 rows that are similar to this: select MEET, count(*) from RATINGS_WHENU where MEET in ('N','Y') and SITE = '63' group by MEET I can run the query again and again, and cannot get it to crash myself, but our applications run this query on regular occasion. Below is output of some recent crashes this am. Any help is appreciated. I reported this or atleast a very similar problem before and I followed the advice to use the most recent MySQL and to alter a few variables which did seem to help for a couple of weeks atleast. Our db traffic really hasn't changed much since then so I am flummoxed as to why now this would resurface. Thanks, Richard F. Rebel. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
