From nobody@FreeBSD.org  Sun Feb 22 04:12:51 2004
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 9C2AE16A4CF
	for <freebsd-gnats-submit@FreeBSD.org>; Sun, 22 Feb 2004 04:12:51 -0800 (PST)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 98A5C43D2F
	for <freebsd-gnats-submit@FreeBSD.org>; Sun, 22 Feb 2004 04:12:51 -0800 (PST)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.12.10/8.12.10) with ESMTP id i1MCCn72059714
	for <freebsd-gnats-submit@FreeBSD.org>; Sun, 22 Feb 2004 04:12:49 -0800 (PST)
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.12.10/8.12.10/Submit) id i1MCCn41059713;
	Sun, 22 Feb 2004 04:12:49 -0800 (PST)
	(envelope-from nobody)
Message-Id: <200402221212.i1MCCn41059713@www.freebsd.org>
Date: Sun, 22 Feb 2004 04:12:49 -0800 (PST)
From: Gabriel Ambuehl <gabriel_ambuehl@buz.ch>
To: freebsd-gnats-submit@FreeBSD.org
Subject: MySQL 4 crashes on CURRENT since 20040221
X-Send-Pr-Version: www-2.3

>Number:         63213
>Category:       misc
>Synopsis:       MySQL 4 crashes on CURRENT since 20040221
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Feb 22 04:20:11 PST 2004
>Closed-Date:    Sat Mar 13 14:27:03 PST 2004
>Last-Modified:  Sat Mar 13 14:27:03 PST 2004
>Originator:     Gabriel Ambuehl
>Release:        5-CURRENT
>Organization:
>Environment:
FreeBSD test 5.2-CURRENT FreeBSD 5.2-CURRENT #2: Sun Feb 22 10:37:08 GMT 2004 root@:/usr/obj/usr/src/sys/GENERIC  i386

HW: Athlon XP2400+, Via KT400, 512MB RAM, Promise RAID1 array on 80GB Maxtor drives. Not known to have any problems, runs through memtest flawlessly. Other machine is based on a VIA EPIA 10000M with 512MB RAM and 3Ware Escalade RAID5 on 120 GB Seagate drives.

>Description:
FreeBSD keeps crashing on CURRENT since yesterday (20040221). More specifically, it will exit on signal 6 during init and later on it will respond to local queries but crash on accepting connections from remote.

Since this happens on two distinct machines which both worked with MySQL on 5.2.1RC2, I'd rule out a problem with the hardware or MySQL release.
>How-To-Repeat:
cvsup to CURRENT, 
install mysql 4 from the ports
try connect to mysql from another host.
>Fix:
      
>Release-Note:
>Audit-Trail:

From: Gabriel Ambuehl <gabriel_ambuehl@buz.ch>
To: freebsd-gnats-submit@FreeBSD.org, gabriel_ambuehl@buz.ch
Cc:  
Subject: Re: misc/63213: MySQL 4 crashes on CURRENT since 20040221
Date: Sun, 22 Feb 2004 13:51:07 +0100

 Obviously it should read MySQL keeps crashing.

From: Erik Greenwald <erik@smluc.org>
To: Gabriel Ambuehl <gabriel_ambuehl@buz.ch>
Cc: freebsd-gnats-submit@freebsd.org
Subject: Re: misc/63213: MySQL 4 crashes on CURRENT since 20040221
Date: Sun, 22 Feb 2004 07:22:39 -0600

 On Sun, Feb 22, 2004 at 04:12:49AM -0800, Gabriel Ambuehl wrote:
 > 
 > HW: Athlon XP2400+, Via KT400, 512MB RAM, Promise RAID1 array on 80GB Maxtor drives. Not known to have any problems, runs through memtest flawlessly. Other machine is based on a VIA EPIA 10000M with 512MB RAM and 3Ware Escalade RAID5 on 120 GB Seagate drives.
 > 
 > >Description:
 > FreeBSD keeps crashing on CURRENT since yesterday (20040221). More specifically, it will exit on signal 6 during init and later on it will respond to local queries but crash on accepting connections from remote.
 > 
 > Since this happens on two distinct machines which both worked with MySQL on 5.2.1RC2, I'd rule out a problem with the hardware or MySQL release.
 > >How-To-Repeat:
 > cvsup to CURRENT, 
 > install mysql 4 from the ports
 > try connect to mysql from another host.
 
 this looks like a dup of ports/62845 ? is it mysql40, or 41?
 
 I've been seeing this the port point upgrade to 4.0.18 (no other system
 upgrade...) , but ale@ has been unable to duplicate it. I'm beginning
 to wonder if it's only happening on amd chips? (I'm running an old
 athlon tbird 850).
 
 Did your mysql-server port get upgraded at the same time? if not,
 mind if I ask when your src before the 20040221 update was updated?
 (I saw it on 20040207 and 20040214)
 
 -- 
         -Erik <erik@smluc.org> [http://math.smsu.edu/~erik]
 
 The opinions expressed by me are not necessarily opinions. In all probability,
 they are random rambling, and to be ignored. Failure to ignore may result in
 severe boredom or confusion. Shake well before opening. Keep Refrigerated.

From: Gabriel Ambuehl <gabriel_ambuehl@buz.ch>
To: Erik Greenwald <erik@smluc.org>
Cc: freebsd-gnats-submit@freebsd.org
Subject: Re[2]: misc/63213: MySQL 4 crashes on CURRENT since 20040221
Date: Sun, 22 Feb 2004 15:31:09 +0100

 Hello Erik,
 
 Sunday, February 22, 2004, 2:22:39 PM, you wrote:
 
 >> Since this happens on two distinct machines which both worked
 >> with MySQL on 5.2.1RC2, I'd rule out a problem with the hardware or
 >> MySQL release.
 >> >How-To-Repeat:
 >> cvsup to CURRENT, 
 >> install mysql 4 from the ports
 >> try connect to mysql from another host.
 
 > this looks like a dup of ports/62845 ? is it mysql40, or 41?
 
 It is 40. I didn't see any MySQL related troubles so I submitted the
 PR.
 
 > I've been seeing this the port point upgrade to 4.0.18 (no other system
 > upgrade...) , but ale@ has been unable to duplicate it. I'm beginning
 > to wonder if it's only happening on amd chips? (I'm running an old
 > athlon tbird 850).
 
 Well on my machines, it happens on both 4.0.17 and 4.0.18 so I'd rule
 out a problem with MySQL (especially as both seem to work flawlessly
 on 4.9). I doubt it's only on Athlon as it happens on the VIA C3 as well. Also I've
 NEVER ever came across any troubles with the Athlons (VIA chipsets
 aren't the greatest but largely don't cause any trouble either).
 Seems to me as it is
 
 Too bad I ain't got no Intel machine handy to check.
 
 > Did your mysql-server port get upgraded at the same time?
 
 Yes and I've rebuilt it twice since to rule out compilation troubles.
 Same for world and kernel, I cvsupped and rebuilt those again today,
 still happening. It seems like there's something wrong with its TCP/IP
 interface (doesn't matter if from localhost or via LAN), as access
 thru the named pipe is working just fine.
 
 > if not,
 > mind if I ask when your src before the 20040221 update was updated?
 > (I saw it on 20040207 and 20040214)
 
 I can't really say. Earlier this week, so sometime around the 18th I'd
 say, definitely taafter the libkse to libpthread change.
 
 
 
 
 
 Best regards,
  Gabriel
 

From: Alex Dupre <sysadmin@alexdupre.com>
To: freebsd-gnats-submit@FreeBSD.org, gabriel_ambuehl@buz.ch
Cc:  
Subject: Re: misc/63213: MySQL 4 crashes on CURRENT since 20040221
Date: Sun, 22 Feb 2004 16:14:29 +0100

 Yes, I still cannot reproduce it:
 
 %uname -a
 FreeBSD armada.alexdupre.com 5.2-CURRENT FreeBSD 5.2-CURRENT #1: Sun Feb 
 22 13:26:46 CET 2004 
 alex@armada.alexdupre.com:/usr/obj/usr/src/sys/ARMADA  i386
 
 mysql> \s
 --------------
 mysql  Ver 12.22 Distrib 4.0.18, for portbld-freebsd5.2 (i386)
 
 Connection id:          3
 Current database:
 Current user:           pippo@armada.alexdupre.com
 SSL:                    Not in use
 Current pager:          more
 Using outfile:          ''
 Server version:         4.0.18
 Protocol version:       10
 Connection:             armada.alexdupre.com via TCP/IP
 Client characterset:    latin1
 Server characterset:    latin1
 TCP port:               3306
 Uptime:                 1 hour 59 min 31 sec
 
 Threads: 2  Questions: 5  Slow queries: 0  Opens: 6  Flush tables: 1 
 Open tables: 0  Queries per second avg: 0.001
 --------------
 

From: Gabriel Ambuehl <gabriel_ambuehl@buz.ch>
To: Alex Dupre <ale@FreeBSD.org>
Cc: freebsd-gnats-submit@FreeBSD.org, freebsd-bugs@FreeBSD.org,
	freebsd-current@freebsd.org
Subject: Re: misc/63213: MySQL 4 crashes on CURRENT since 20040221
Date: Tue, 9 Mar 2004 10:44:37 +0100

 Hello Alex,
 Thursday, February 26, 2004, 10:25:59 AM, you wrote:
 
 [Mysql 4.0.18 crashing when trying to connect via TCP/IP as opposed
 to via the pipe]
 
 >> Yes. As I said, it works perfectly on 5.2.1RC2, but fails on connects
 >> via TCP/IP since at least 2004/02/20 builds (newest cvsup I checked
 >> was as of today). (using vanilla make.conf and GENERIC) Fails on both AMD and Via
 >> C3 CPUs, no Intel box around, so I can't check that.
 
 > Here:
 
 > 5.2-CURRENT #0: Tue Feb 24 12:04:01 CET 2004
 
 > CPUTYPE?=p3
 > CFLAGS= -O -pipe
 > CXXFLAGS+= -fmemoize-lookups -fsave-memoized
 
 > working.
 
 
 Still occuring on both machines mentioned above on
 5.2-CURRENT FreeBSD 5.2-CURRENT #3: Mon Mar  8 18:20:32 GMT 2004
 when using libkse OR libc_r.
 
 
 Best regards,
  Gabriel
 
State-Changed-From-To: open->closed 
State-Changed-By: ale 
State-Changed-When: Sat Mar 13 14:26:04 PST 2004 
State-Changed-Why:  
Duplicate of PR 62845. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=63213 
>Unformatted:
