Richard, looks like a clean case of memory corruption.
Your log sequence number is only 29 MB. You got problems very quickly. I regularly run tests where gigabytes of log are generated, and no crash. Linux-2.4.20 has the reputation of being stable. This might even be a hardware problem. Best regards, 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 MySQL Order MySQL technical support from https://order.mysql.com/ ----- Original Message ----- From: "Richard Runds" <[EMAIL PROTECTED]> Newsgroups: mailing.database.myodbc Sent: Friday, October 03, 2003 4:24 PM Subject: mysqld crash > >Description: > Upon starting mysql client with the following command: > mysql -ppassword radiant > Immediately error message where displayed, one per table, saying that > the table existed, however no columns/fields where found. > Unfortunately I do not have the logs of this, as these logs where > to stdout, rather than the log file. However, the log file did > contain a difference set of errors, at this time, and is included in > this mail. > > Here is the .err file from the machine: > > 030819 15:42:06 mysqld started > 030819 15:42:06 InnoDB: Started > /usr/sbin/mysqld: ready for connections. > Version: '4.0.14-standard' socket: '/var/lib/mysql/mysql.sock' port: 3306 > 031002 13:20:35 InnoDB: Assertion failure in thread 800935949 in file ut0mem.c line > 157 > InnoDB: Failing assertion: block->magic_n == UT_MEM_MAGIC_N > 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 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=8388600 > read_buffer_size=131072 > max_used_connections=22 > max_connections=100 > threads_connected=4 > It is possible that mysqld could use up to > key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225791 K > bytes of memory > Hope that's ok; if not, decrease some variables in the equation. > > thd=0x41714fd8 > 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... > Cannot determine thread, fp=0xbfe1f308, backtrace may not be correct. > Stack range sanity check OK, backtrace follows: > 0x807474f > 0x82a0ad8 > 0x8244c7d > 0x8243028 > 0x8241c21 > 0x813c3d4 > 0x80d6899 > 0x8097901 > 0x809517c > 0x828a3b5 > 0x80952ee > 0x807ef22 > 0x80844ee > 0x807d79f > 0x829e28c > 0x82d199a > New value of fp=(nil) failed sanity check, terminating stack trace! > Please read http://www.mysql.com/doc/en/Using_stack_trace.html and follow instructio > ns on how to resolve the stack trace. Resolved > 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 0x88bbc30 = > thd->thread_id=9632717 > The manual page at http://www.mysql.com/doc/en/Crashing.html contains > information that should help you find out what is causing the crash. > > Number of processes running now: 0 > 031002 13:20:36 mysqld restarted > 031002 13:20:36 InnoDB: Database was not shut down normally. > InnoDB: Starting recovery from log files... > InnoDB: Starting log scan based on checkpoint at > InnoDB: log sequence number 0 28715608 > InnoDB: Doing recovery: scanned up to log sequence number 0 28715608 > 031002 13:20:36 InnoDB: Flushing modified pages from the buffer pool... > 031002 13:20:36 InnoDB: Started > /usr/sbin/mysqld: ready for connections. > Version: '4.0.14-standard' socket: '/var/lib/mysql/mysql.sock' port: 3306 > > > Here is the symbol dump of the backtrace: > > 0x807474f handle_segfault + 423 > 0x82a0ad8 pthread_sighandler + 184 > 0x8244c7d ut_free + 209 > 0x8243028 mem_area_free + 48 > 0x8241c21 mem_heap_block_free + 385 > 0x813c3d4 row_prebuilt_free + 444 > 0x80d6899 close__11ha_innobase + 25 > 0x8097901 closefrm__FP8st_table + 45 > 0x809517c free_cache_entry__FP8st_table + 36 > 0x828a3b5 hash_delete + 813 > 0x80952ee close_thread_tables__FP3THDb + 174 > 0x807ef22 dispatch_command__F19enum_server_commandP3THDPcUi + 3886 > 0x80844ee do_command__FP3THD + 154 > 0x807d79f handle_one_connection + 635 > 0x829e28c pthread_start_thread + 220 > 0x82d199a thread_start + 4 > > > >How-To-Repeat: > We have not been able to recreate this problem. We have logged into > the mysql client many times since, and have not seen this error > again. > >Fix: > None. > > >Submitter-Id: > >Originator: root > >Organization: > Richard Runds > >MySQL support: none > >Synopsis: mysqld on off crash > >Severity: critical > >Priority: high > >Category: mysql > >Class: sw-bug > >Release: mysql-4.0.14-standard (Official MySQL RPM) > > >C compiler: 2.95.3 > >C++ compiler: 2.95.3 > >Environment: > dell, linux redhat 9.0, i686 > System: Linux radiant-cgh.rieo.cgh 2.4.20-19.9custom #3 Tue Aug 12 15:47:29 GMT 2003 i686 i686 i386 GNU/Linux > 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/3.2.2/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zli b --enable-__cxa_atexit --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5) > Compilation info: CC='gcc' CFLAGS='-O6 -fno-omit-frame-pointer -mpentium' CXX='g++' '-O6 -fno-omit-frame-pointer -felide-constructors -fno-exceptions -fno-rtti -mpentium' LDFLAGS='' ASFLAGS='' > LIBC: > lrwxrwxrwx 1 root root 13 Aug 5 14:57 /lib/libc.so.6 -> libc-2.3.2.so > -rwxr-xr-x 1 root root 1557296 Apr 8 00:25 /lib/libc-2.3.2.so > -rw-r--r-- 1 root root 2331360 Apr 7 23:34 /usr/lib/libc.a > -rw-r--r-- 1 root root 204 Apr 7 23:07 /usr/lib/libc.so > Configure command: ./configure '--disable-shared' '--with-mysqld-ldflags=-all-static' '--with-client-ldflags=-all-static' '--with-server-suffix=-standard' '--without-berkeley-db' '--with-innodb' '--without-vio' '--without-openssl' '--enable-assembler' '--enable-local-infile' '--with-mysqld-user=mysql' '--with-unix-socket-path=/var/lib/mysql/mysql.sock' '--prefix=/' '--with-extra-charsets=complex' '--exec-prefix=/usr' '--libexecdir=/usr/sbin' '--libdir=/usr/lib' '--sysconfdir=/etc' '--datadir=/usr/share' '--localstatedir=/var/lib/mysql' '--infodir=/usr/share/info' '--includedir=/usr/include' '--mandir=/usr/share/man' '--with-embedded-server' '--enable-thread-safe-client' '--with-comment=Official MySQL RPM' 'CC=' 'CFLAGS=-O6 -fno-omit-frame-pointer -mpentium' 'CXXFLAGS=-O6 -fno-omit-frame-pointer -felide-constructors -fno-ex ceptions -fno-rtti -mpentium' 'CXX=' > > > > -- > 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]
