Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 22 Feb 2004 06:30:13 -0800 (PST)
From:      Gabriel Ambuehl <gabriel_ambuehl@buz.ch>
To:        freebsd-bugs@FreeBSD.org
Subject:   Re[2]: misc/63213: MySQL 4 crashes on CURRENT since 20040221
Message-ID:  <200402221430.i1MEUDpf067186@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR misc/63213; it has been noted by GNATS.

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
 



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200402221430.i1MEUDpf067186>