Hi Joshua, First thing I'd try is upgrading to 4.1.1! And/or 4.1.2 when it's released in a couple weeks.
Matt ----- Original Message ----- From: "Joshua Thomas" Sent: Monday, March 29, 2004 10:51 AM Subject: mysqld keeps crashing > Hello all, > > I'm running mysql 4.1.0-alpha-log on FreeBSD 5.1, with InnoDB. > > In the last month, I've had a number crashes, and table corruption. My > application is a website of medium volume, and the database is not more than > a few hundred MB. The errors I recieve are almost all signal 11 errors. > > Here's some of what I have, from mysql_error_log: > > -- > InnoDB: Scanning backward trying to find previous allocated mem blocks > Mem block at - 68, file w0sel.c, line 2457 > Freed mem block at - 324, file w0sel.c, line 2457 > Mem block at - 580, file mysql.c, line 324 > Mem block at - 836, file w0ins.c, line 82 > Mem block at - 964, file m0rec.c, line 443 > Mem block at - 1092, file m0rec.c, line 443 > Mem block at - 1348, file 0pcur.c, line 28 > Mem block at - 1604, file w0upd.c, line 287 > Mem block at - 1732, file 0pcur.c, line 162 > Mem block at - 1860, file m0rec.c, line 443 > InnoDB: Scanning forward trying to find next allocated mem blocks > Mem block at + 188, file mysql.c, line 324 > Freed mem block at + 2236, file w0sel.c, line 2128 > Mem block at + 8380, file w0ins.c, line 82 > Mem block at + 10428, file w0ins.c, line 82 > Mem block at + 12476, file w0ins.c, line 82 > Mem block at + 16572, file mysql.c, line 324 > Mem block at + 24764, file w0ins.c, line 82 > Freed mem block at + 28860, file x0trx.c, line 78 > Mem block at + 29372, file t0mem.c, line 197 > Mem block at + 29884, file t0mem.c, line 197 > 040328 12:49:29 InnoDB: Assertion failure in thread 358640640 in file > row0mysql > .c line 452 > 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 bin ary > 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=33554432 > read_buffer_size=131072 > sort_buffer_size=2097144 > max_used_connections=46 > max_connections=500 > threads_connected=1 > It is possible that mysqld could use up to > key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = > 112076 > 4 K > bytes of memory > Hope that's ok; if not, decrease some variables in the equation. > > 040328 12:49:29 mysqld restarted > -- > > > Thanks in advance, > Joshua Thomas -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
