List:General Discussion« Previous MessageNext Message »
From:Michael Bacarella Date:May 15 2002 6:33pm
Subject:Assertion failure with mysql-3.23.49a/InnoDB
View as plain text  
I've gotten this same assertion failure twice.

I'm very confident in this machine's stability since it has survived 36 hours
worth of CTCS, so I'm not going to look for a hardware problem just yet.

At first I thought it may have been the glibc issue with threads overwriting
each other's stacks but this time possible memory use is well under 2GB.

I tried to resolve the symbols but the mysql binary doesn't appear to
come with debugging symbols (or at least any that ``nm'' was able to find).

Using the mysql-max-3.23.49a-pc-linux-gnu-i686 tarball binary

Hopefully someone has seen this before??


/usr/local/mysql/bin/mysqld: ready for connections
InnoDB: Assertion failure in thread 61456 in file ../include/page0page.ic line 515
InnoDB: We intentionally generate a memory trap.
InnoDB: Send a detailed bug report to mysql@stripped
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.
InnoDB: Thread 446574 stopped in file os0sync.c line 395
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=67104768
InnoDB: Thread 266306 stopped in file sync0arr.c line 336
InnoDB: Thread 8195 stopped in file os0sync.c line 115
InnoDB: Thread 12292 stopped in file os0file.c line 1175
record_buffer=131072
sort_buffer=4194296
max_used_connections=121
max_connections=300
threads_connected=60
It is possible that mysqld could use up to 
key_buffer_size + (record_buffer + sort_buffer)*max_connections = 1332729 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:
0x806dc04
0x82ad1a8
0x81d19c7
0x81d3077
0x81ba8e0
0x8193681
0x80bf5aa
0x80c0ded
0x8093962
0x809372b
0x808b704
0x8074a4a
0x8078b48
0x8073c24
0x8072fd7

Some mysqlbug output:

System: Linux fileserv 2.4.7-10smp #1 SMP Thu Sep 6 17:09:31 EDT 2001 i686 unknown
Architecture: i686

Some paths:  /usr/bin/perl /usr/bin/make /usr/bin/gmake /usr/bin/gcc /usr/bin/cc
GCC: Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/2.96/specs
gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-98)
Compilation info: CC='gcc'  CFLAGS='-Wimplicit -Wreturn-type -Wid-clash-51 -Wswitch
-Wtrigraphs -Wcomment -W -Wchar-subscripts -Wformat -Wimplicit-function-dec
-Wimplicit-int -Wparentheses -Wsign-compare -Wwrite-strings -Wunused -mcpu=pentiumpro -O3
-fno-omit-frame-pointer'  CXX='gcc'  CXXFLAGS='-Wimplicit -Wreturn-type -Wid-clash-51
-Wswitch -Wtrigraphs -Wcomment -W -Wchar-subscripts -Wformat -Wimplicit-function-dec
-Wimplicit-int -Wparentheses -Wsign-compare -Wwrite-strings -Woverloaded-virtual
-Wextern-inline -Wsign-promo -Wreorder -Wctor-dtor-privacy -Wnon-virtual-dtor
-felide-constructors -fno-exceptions -fno-rtti -mcpu=pentiumpro -O3
-fno-omit-frame-pointer'  LDFLAGS=''
LIBC:
lrwxrwxrwx    1 root     root           13 Feb 22 10:38 /lib/libc.so.6 -> libc-2.2.4.so
-rwxr-xr-x    1 root     root      1282588 Sep  4  2001 /lib/libc-2.2.4.so
-rw-r--r--    1 root     root     27304836 Sep  4  2001 /usr/lib/libc.a
-rw-r--r--    1 root     root          178 Sep  4  2001 /usr/lib/libc.so
Configure command: ./configure --prefix=/usr/local/mysql --enable-assembler
--with-extra-charsets=complex --enable-thread-safe-client --with-innodb
--with-berkeley-db --enable-thread-safe-client --with-other-libc=/usr/local/mysql-glibc
'--with-comment=Official MySQL Binary' --prefix=/usr/local/mysql
--with-extra-charset=complex --enable-thread-safe-client --enable-local-infile
--with-server-suffix=-max 'CFLAGS=-Wimplicit -Wreturn-type -Wid-clash-51 -Wswitch
-Wtrigraphs -Wcomment -W -Wchar-subscripts -Wformat -Wimplicit-function-dec
-Wimplicit-int -Wparentheses -Wsign-compare -Wwrite-strings -Wunused -mcpu=pentiumpro -O3
-fno-omit-frame-pointer' 'CXXFLAGS=-Wimplicit -Wreturn-type -Wid-clash-51 -Wswitch
-Wtrigraphs -Wcomment -W -Wchar-subscripts -Wformat -Wimplicit-function-dec
-Wimplicit-int -Wparentheses -Wsign-compare -Wwrite-strings -Woverloaded-virtual
-Wextern-inline -Wsign-promo -Wreorder -Wctor-dtor-privacy -Wnon-virtual-dtor
-felide-constructors -fno-exceptions -fno-rtti -mcpu=pentiumpro -O3
-fno-omit-frame-pointer' CXX=gcc

-- 
Michael Bacarella  | Netgraft Corporation
                   | 545 Eighth Ave #401
 Systems Analysis  | New York, NY 10018
Technical Support  | 212 946-1038 | 917 670-6982
 Managed Services  | mbac@stripped

Thread
Assertion failure with mysql-3.23.49a/InnoDBMichael Bacarella15 May
Re: Assertion failure with mysql-3.23.49a/InnoDBHeikki Tuuri15 May