Re: Persistant Index Problems and mySQL crashing.

[Paul Czarnik]

We have similiar problem. On 4.1.10a and 4.1.11 we receive rarely "mysqld got signal 11;" in logs,
and sometimes our indexes are broken - we have to "REPAIR TABLE name" when this occurs.

Our db is rarelly used, so this is not so annyoing but still it's a serious bug.

OS: Debian (amd64 with linux kernel 2.6.10)

gcc --version
gcc (GCC) 3.3.5 (Debian 1:3.3.5-12)

cat /proc/cpuinfo
model name : AMD Athlon(tm) 64 Processor 3000+

Sources was compiled with options:
CFLAGS="-O2" CXX=gcc CXXFLAGS="-O2 -felide-constructors \
-fno-exceptions -fno-rtti" ./configure \
--prefix=/usr/local/mysql-4.1.11 \
--with-extra-charsets=all --enable-thread-safe-client \
--without-innodb \
--without-docs \
--without-man \
--without-bench \
--disable-shared \
--with-mysqld-ldflags=-all-static

./configure was manually patched to not forcing to use LinuxThreads because debian have NTPL. This issue was reporter last year and still has not been fixed :/

in log we have only:
<log>
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=134217728
read_buffer_size=1044480
max_used_connections=1
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 335471 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.


Number of processes running now: 0
050408 09:42:24 mysqld restarted
</log>