niestabilny mysql

[Zbyniu Krzystolik]

Mniej wiecej Tue, Nov 22, 2005 at 11:47:41AM +0100, zainteresowany Andrzej 'The Undefined' Dopierała rzekl:
> nowa maszynka na amd64(wczesniej byl athlon), bazy przeniesione i co
> jakiś czas mysql (5.0.15, wcześniej był 4.1) się wykrzacza.
> W logu:
> *** glibc detected *** realloc(): invalid pointer: 0x0000000001349510 ***
> *** glibc detected *** free(): invalid next size (fast): 0x000000000134c170 ***
> mysqld got signal 6;
> 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=4
> max_connections=100
> threads_connected=2
> 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.

Miałem takie coś na i686, dump baz i load pomógł, dawało się wywołać ten
efekt konkretnym zapytaniem (jakieś z 4-krotnym JOINem)

mysql-5.0.15-4
glibc-2.3.5-8
db-4.2.52-11
kernel24-2.4.31-2

i na replice
kernel-vserver-smp-2.6.11.12-3.1
reszta j.w.

Zbyniu
-- 
%% Absolutely nothing we trust %%