misc/63213: MySQL 4 crashes on CURRENT since 20040221

[Erik Greenwald]

The following reply was made to PR misc/63213; it has been noted by GNATS.

From: Erik Greenwald <erik at smluc.org>
To: Gabriel Ambuehl <gabriel_ambuehl at buz.ch>
Cc: freebsd-gnats-submit at 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 at 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.