MySQL startet nicht

[Wolfgang Rhein]

Hallo Mailliste,

ich habe ein Problem, mein MySQL-Server läst sich nicht zum laufen
bewegen.
Ich verwende MySQL vom SuSE  in der Version mysql-3.23.44-24 auf SuSE
7.3.
Der Server stirbt einfach und ich weis nicht was ich noch machen soll,
selbst die Neuinstallation hat nicht gebracht.

Ich gebe euch mal *.err als auch die Debuglog mit und hoff das ihr mir
weiter helfen könnt.

Debuglog:  

SEND-PR: -*- send-pr -*-
SEND-PR: Lines starting with `SEND-PR' will be removed automatically, as
SEND-PR: will all comments (text enclosed in `<' and `>').
SEND-PR:
From: root
To: mysql@lists.mysql.com
Subject: [50 character or so descriptive subject here (for reference)]

>Description:
	<precise description of the problem (multiple lines)>
>How-To-Repeat:
	<code/input/activities to reproduce the problem (multiple
lines)>
>Fix:
	<how to correct or work around the problem, if known (multiple
lines)>

>Submitter-Id:	<submitter ID>
>Originator:	root
>Organization:
 <organization of PR author (multiple lines)>
>MySQL support: [none | licence | email support | extended email support
]
>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.44 (Source distribution)

>Environment:
	<machine, os, target, libraries (multiple lines)>
System: Linux wuwell1 2.4.16-4GB #1 Mon Apr 15 08:57:26 GMT 2002 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/i486-suse-linux/2.95.3/specs
gcc version 2.95.3 20010315 (SuSE)
Compilation info: CC='gcc'  CFLAGS=''  CXX='c++'  CXXFLAGS='-O2
-mcpu=i486 -march=i486                  -D_FILE_OFFSET_BITS=64
-D_LARGEFILE_SOURCE                  -felide-constructors
-fno-exceptions 				 -fno-rtti'  LDFLAGS=''
LIBC: 
-rwxr-xr-x    1 root     root      1384072 Oct  1 18:10 /lib/libc.so.6
-rw-r--r--    1 root     root     25215016 Oct  1 17:56 /usr/lib/libc.a
-rw-r--r--    1 root     root          178 Oct  1 17:56 /usr/lib/libc.so
-rw-r--r--    1 root     root       856542 Sep 24  2001
/usr/lib/libc-client.a
lrwxrwxrwx    1 root     root           20 Jan 24  2002
/usr/lib/libc-client.so -> libc-client.so.2000c
-rwxr-xr-x    1 root     root       718160 Sep 24  2001
/usr/lib/libc-client.so.2000c
Configure command: ./configure  --disable-shared
--with-mysqld-ldflags='-all-static' --with-client-ldflags='-all-static'
--without-berkeley-db --without-innodb --enable-assembler
--enable-large-files --infodir=/usr/share/info --libdir=/usr/lib
--libexecdir=/usr/sbin --localstatedir=/var/lib/mysql
--mandir=/usr/share/man --prefix=/usr --sysconfdir=/etc
--with-mysqld-user=mysql --without-debug --datadir=/usr/share
--includedir=/usr/include --with-extra-charsets=complex
--with-unix-socket-path=/var/lib/mysql/mysql.sock --with-libwrap

*.err:
030107 05:28:06  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=16773120
record_buffer=131072
sort_buffer=524280
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 = 80379
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=0xbfffdb58,
stack_bottom=0x7445f910, thread_stack=65536, aborting backtrace.
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x73311e10  is invalid pointer
thd->thread_id=829319543

Successfully dumped variables, if you ran with --log, take a look at the
details of what thread 829319543 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
030107 05:28:06  mysqld ended

Vorab Danke

Gruß

Wolfgang Rhein


-- 
Infos zur Mailingliste, zur Teilnahme und zum An- und Abmelden unter
-->>  http://www.4t2.com/mysql