7 messages in com.mysql.lists.bugsRe: mysqld got signal 11
FromSent OnAttachments
Carlos Perdones19 Apr 2001 06:44 
Sinisa Milivojevic19 Apr 2001 06:52 
Michael Widenius19 Apr 2001 11:51 
Sasha Pachev19 Apr 2001 16:29 
Carlos Perdones25 Apr 2001 08:03 
Sinisa Milivojevic26 Apr 2001 05:02 
Sasha Pachev26 Apr 2001 10:59 
Subject:Re: mysqld got signal 11
From:Sinisa Milivojevic (sin@mysql.com)
Date:04/19/2001 06:52:01 AM
List:com.mysql.lists.bugs

Carlos Perdones writes:

Hello,

Red Hat Linux release 6.2 (Zoot) Linux 2.2.14-5.0smp glibc-2.1.3-21 java version "1.2.2-RC2" Classic VM (build 1.2.2-RC2-K, green threads, javacomp)

#mysqladmin

Ver 8.18 Distrib 3.23.36, for pc-linux-gnu on i686 Copyright (C) 2000 MySQL AB & MySQL Finland AB & TCX DataKonsult AB This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to modify and redistribute it under the GPL license

Server version 3.23.36 Protocol version 10 Connection Localhost via UNIX socket UNIX socket /tmp/mysql.sock Uptime: 1 hour 42 min 42 sec

Threads: 57 Questions: 549899 Slow queries: 0 Opens: 56 Flush tables: 1 Open tables: 50 Queries per second avg: 89.240

This is the problem when the server automatically restart

==========================================================================

numero de procesos xrealloc: realloc(905) failedCannot allocate memory

110

BUG IN DYNAMIC LINKER ld.so: dl-minimal.c: 69: malloc: Assertion `page != ((void *) -1)' failed!

============================================================================ ===========

mysqld got signal 11; The manual section 'Debugging a MySQL server' tells you how to use a stack trace and/or the core file to produce a readable backtrace that may help in finding out why mysqld died. 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... Stack range sanity check OK, backtrace follows: 0x813586a 0x8116f90 0x8116c11 0x80fbdfd 0x80f834a 0x80f7d64 0x80f7ea0 0x80c8997 0x80aa420 0x80a53df 0x80a51b6 0x809e416 0x808336d 0x8087353 0x8082769 0x8081c96 Stack trace successful, trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x8b52850 = SELECT COUNT(*) as nregs FROM genteirc WHERE OK='1' thd->thread_id = 194334 Successfully dumped variables, if you ran with --log, take a look at the details of what thread 194334 did to cause the crash. In some cases of really bad corruption, this value may be invalid Please use the information above to create a repeatable test case for the crash, and send it to bu@lists.mysql.com

Number of processes running now: 0 010419 13:37:32 mysqld restarted /usr/local/mysql/libexec/mysqld: ready for connections

Regards

Hi!

Can you let us know what kind of query did cause the above ??

Do you have a binary or update log, so that you could pinpoint a query that causes the above ??

Also, are you using our binary ??

Regards,

Sinisa

____ __ _____ _____ ___ == MySQL AB /*/\*\/\*\ /*/ \*\ /*/ \*\ |*| Sinisa Milivojevic /*/ /*/ /*/ \*\_ |*| |*||*| mailto:sin@mysql.com /*/ /*/ /*/\*\/*/ \*\|*| |*||*| Larnaca, Cyprus /*/ /*/ /*/\*\_/*/ \*\_/*/ |*|____ ^^^^^^^^^^^^/*/^^^^^^^^^^^\*\^^^^^^^^^^^ /*/ \*\ Developers Team