Hi,
here is my half selfmade :) bug report.
I´ve tried this on different machine with different linux version (other
one is linux 2.2.18)
And I also tried more RAM (512 MB ) without any change to the error.
Maybe you can help me :
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject:
Instant Mysql server crash problem with berkeley db enabled
>Description:
Mysql crash after invoking with :
safe_mysqld --skip-bdb --bdb-no-recover --log --skip-locking
>How-To-Repeat:
>Fix:
????????????????????
>Submitter-Id: <submitter ID>
>Originator: root
>Organization:
>MySQL support: none
>Synopsis: <synopsis of the problem (one line)>
>Severity: <[ non-critical | serious | critical ] (one line)>
>Priority: <[ low | medium | high ] (one line)>
>Category: mysql
>Class: <[ sw-bug | doc-bug | change-request | support ] (one
line)>
>Release: mysql-3.23.43 (Source distribution)
>Environment:
<machine, os, target, libraries (multiple lines)>
System: Linux BoH 2.4.10 #1 Sat Oct 6 13:40:44 CEST 2001 i686 unknown
Architecture: i686
Some paths: /usr/bin/perl /usr/bin/make /usr/bin/gcc /usr/bin/cc
GCC: Reading specs from /usr/lib/gcc-lib/i486-linux/egcs-2.91.66/specs
gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)
Compilation info: CC='gcc' CFLAGS='' CXX='c++' CXXFLAGS='' LDFLAGS=''
LIBC:
lrwxrwxrwx 1 root root 13 Feb 10 2001 /lib/libc.so.4 ->
libc.so
.4.7.6
-rwxr-xr-x 1 root root 634880 Apr 29 1996 /lib/libc.so.4.7.6
-rwxr-xr-x 1 root root 4190668 Jul 22 1999 /lib/libc.so.6
-rw-r--r-- 1 root root 19921908 Jul 22 1999 /usr/lib/libc.a
-rw-r--r-- 1 root root 178 Jul 22 1999 /usr/lib/libc.so
Configure command: ./configure --with-berkeley-db
Perl: This is perl, version 5.005_03 built for i586-linux
CPU states: 97.8% user, 2.8% system, 98.8% nice, 0.0% idle
Mem: 126608K av, 122924K used, 3684K free, 0K shrd, 3112K buff
Swap: 131536K av, 0K used, 131536K free 54592K cached
Error Message from mysqld :
011025 00:37:14 mysqld started
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.
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
record_buffer=131072
sort_buffer=2097144
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (record_buffer + sort_buffer)*max_connections = 225791 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...
Bogus stack limit or frame pointer, fp=0xbfffec9c,
stack_bottom=0x6070607, threa
d_stack=65536, aborting backtrace.
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x6070607 is invalid pointer
thd->thread_id=2
Successfully dumped variables, if you ran with --log, take a look at the
details of what thread 2 did to cause the crash. In some cases of really
bad corruption, the values shown above may be invalid
The manual page at http://www.mysql.com/doc/C/r/Crashing.html contains
information that should help you find out what is causing the crash
011025 00:37:14 mysqld ended
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
