Re: mysql-20021125BK mysqld crash - Sinisa Milivojevic - com.mysql.lists.bugs

9 messages in com.mysql.lists.bugsRe: mysql-20021125BK mysqld crash

From	Sent On	Attachments
Martin MOKREJŠ	05 Dec 2002 05:30
Sinisa Milivojevic	05 Dec 2002 05:41
Jocelyn Fournier	05 Dec 2002 05:47
Martin MOKREJŠ	05 Dec 2002 06:43
Sinisa Milivojevic	05 Dec 2002 08:47
Michael Widenius	10 Dec 2002 06:58
Martin MOKREJŠ	11 Dec 2002 07:00
Sinisa Milivojevic	11 Dec 2002 07:50
Martin MOKREJŠ	11 Dec 2002 08:04

Subject:	Re: mysql-20021125BK mysqld crash
From:	Sinisa Milivojevic (sin...@mysql.com)
Date:	12/05/2002 05:41:24 AM
List:	com.mysql.lists.bugs

=?iso-8859-2?Q?Martin_MOKREJ=A9?= writes:

Hi, we have observer a mysqld crash. mysqld_safe did not manage to restart mysql at all, maybe there's a bug in the restarting procedure?

How-To-Repeat:

key_buffer_size=268431360 read_buffer_size=1044480 sort_buffer_size=2097144 max_used_connections=21 max_connections=100 threads_connected=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 568939
K bytes of memory Hope that's ok; if not, decrease some variables in the equation. [...]

I cannot say how to reproduce. I tried with most of our databases that have so
many entries, but no problem reappeared. But maybe it helps you anyway.

Linux 2.4.20-pre5-ac1 SMP -- yes, I've already prepared 2.4.20 release kernel.
;)

Hi!

You know we require reproducible test cases.

A stack dump does not tell much , usually ....