misc/63213: MySQL 4 crashes on CURRENT since 20040221

[Gabriel Ambuehl]

>Number:         63213
>Category:       misc
>Synopsis:       MySQL 4 crashes on CURRENT since 20040221
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Feb 22 04:20:11 PST 2004
>Closed-Date:
>Last-Modified:
>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:
>Unformatted: