Your message dated Mon, 9 Jan 2006 22:52:18 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Closing bug report
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 3 Oct 2005 21:50:51 +0000
>From [EMAIL PROTECTED] Mon Oct 03 14:50:50 2005
Return-path: <[EMAIL PROTECTED]>
Received: from wvbg.bndlg.de [194.95.207.31] 
        by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
        id 1EMYCw-0001R3-00; Mon, 03 Oct 2005 14:50:50 -0700
Received: from localhost (wvbg.bndlg.de [127.0.0.1])
        by wvbg.bndlg.de (Postfix) with ESMTP id 2CC59340A3B32
        for <[EMAIL PROTECTED]>; Mon,  3 Oct 2005 23:50:47 +0200 (CEST)
Received: by wvbg.bndlg.de (Postfix, from userid 0)
        id 74EB8340A3B30; Mon,  3 Oct 2005 23:50:46 +0200 (CEST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Michael Vistein <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: mysql-server: MySQL crashes after heavy querying
X-Mailer: reportbug 3.8
Date: Mon, 03 Oct 2005 23:50:46 +0200
Message-Id: <[EMAIL PROTECTED]>
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at fsn.by.schule.de
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02

Package: mysql-server
Version: 4.0.24-10sarge1
Severity: important

While querying MySQL heavily, the server crashes after several querys.
For example, the "Checking for crashed MySQL tables in the background" job on
startup doesn't complete. Or you can't mysqldump every database alone. If you
run mysqldump for the whole server, it works, but not for each database alone.

Syslog shows the following message:

Oct  3 23:41:35 wvbg mysqld[19517]: mysqld got signal 11;
Oct  3 23:41:35 wvbg mysqld[19517]: This could be because you hit a bug. It is 
also possible that this binary
Oct  3 23:41:35 wvbg mysqld[19517]: or one of the libraries it was linked 
against is corrupt, improperly built,
Oct  3 23:41:35 wvbg mysqld[19517]: or misconfigured. This error can also be 
caused by malfunctioning hardware.
Oct  3 23:41:35 wvbg mysqld[19517]: We will try our best to scrape up some info 
that will hopefully help diagnose
Oct  3 23:41:35 wvbg mysqld[19517]: the problem, but since we have already 
crashed, something is definitely wrong
Oct  3 23:41:35 wvbg mysqld[19517]: and this may fail.
Oct  3 23:41:35 wvbg mysqld[19517]:
Oct  3 23:41:35 wvbg mysqld[19517]: key_buffer_size=16777216
Oct  3 23:41:35 wvbg mysqld[19517]: read_buffer_size=131072
Oct  3 23:41:35 wvbg mysqld[19517]: max_used_connections=2
Oct  3 23:41:35 wvbg mysqld[19517]: max_connections=100
Oct  3 23:41:35 wvbg mysqld[19517]: threads_connected=1
Oct  3 23:41:35 wvbg mysqld[19517]: It is possible that mysqld could use up to
Oct  3 23:41:35 wvbg mysqld[19517]: key_buffer_size + (read_buffer_size + 
sort_buffer_size)*max_connections = 233983 K
Oct  3 23:41:35 wvbg mysqld[19517]: bytes of memory
Oct  3 23:41:35 wvbg mysqld[19517]: Hope that's ok; if not, decrease some 
variables in the equation.
Oct  3 23:41:35 wvbg mysqld[19517]:
Oct  3 23:41:35 wvbg mysqld_safe[19565]: Number of processes running now: 0
Oct  3 23:41:35 wvbg mysqld_safe[19567]: restarted

So the server stays more or less usable, because mysql is restarted immediatly,
but some connections are lost every time.
The server has 1024MB RAM, so using 233 MB for MySQL should not be a problem.

-- System Information:
Debian Release: 3.1
Architecture: ia64
Kernel: Linux 2.4.25-hpe-11-mckinley-smp
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages mysql-server depends on:
ii  adduser          3.63                    Add and remove users and groups
ii  debconf          1.4.30.13               Debian configuration management sy
ii  libc6.1          2.3.2.ds1-22            GNU C Library: Shared libraries an
ii  libdbi-perl      1.46-6                  Perl5 database interface by Tim Bu
ii  libgcc1          1:3.4.3-13              GCC support library
ii  libmysqlclient12 4.0.24-10sarge1         mysql database client library
ii  libstdc++5       1:3.3.5-13              The GNU Standard C++ Library v3
ii  libwrap0         7.6.dbs-8               Wietse Venema's TCP wrappers libra
ii  mailx            1:8.1.2-0.20040524cvs-4 A simple mail user agent
ii  mysql-client     4.0.24-10sarge1         mysql database client binaries
ii  mysql-common     4.0.24-10sarge1         mysql database common files (e.g. 
ii  passwd           1:4.0.3-31sarge5        change and administer password and
ii  perl             5.8.4-8                 Larry Wall's Practical Extraction 
ii  psmisc           21.5-1                  Utilities that use the proc filesy
ii  zlib1g           1:1.2.2-4.sarge.2       compression library - runtime

-- debconf information:
  mysql-server/nis_warning:
  mysql-server/really_downgrade_from_41: false
  mysql-server/mysql_update_hints1:
  mysql-server/start_on_boot: true
  mysql-server/postrm_remove_databases: false
* mysql-server/mysql_install_db_notes:

---------------------------------------
Received: (at 331539-done) by bugs.debian.org; 9 Jan 2006 21:52:19 +0000
>From [EMAIL PROTECTED] Mon Jan 09 13:52:19 2006
Return-path: <[EMAIL PROTECTED]>
Received: from gate.lathspell.de ([212.117.68.82] helo=app109.intern)
        by spohr.debian.org with esmtp (Exim 4.50)
        id 1Ew4w7-0001LV-9L
        for [EMAIL PROTECTED]; Mon, 09 Jan 2006 13:52:19 -0800
Received: by app109.intern (Postfix, from userid 1000)
        id 6C29E2C22B; Mon,  9 Jan 2006 22:52:18 +0100 (CET)
Date: Mon, 9 Jan 2006 22:52:18 +0100
From: Christian Hammers <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Closing bug report
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
Content-Disposition: inline
User-Agent: Mutt/1.5.11
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no 
        version=2.60-bugs.debian.org_2005_01_02

This bug has been too long open tagged as unreproducible and moreinfo
so that I don't think that I can help here anymore.

bye,

-christian-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to