ports/62845: update of mysql40-server causes mysqld to segfault on remote connection

Erik Greenwald erik at smluc.org
Sat Feb 14 18:10:07 UTC 2004


>Number:         62845
>Category:       ports
>Synopsis:       update of mysql40-server causes mysqld to segfault on remote connection
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Feb 14 10:10:06 PST 2004
>Closed-Date:
>Last-Modified:
>Originator:     Erik Greenwald
>Release:        FreeBSD 5.2-CURRENT i386
>Organization:
>Environment:
System: FreeBSD fenris 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Sat Feb 7 14:32:45 EST 2004 root at fenris:/usr/obj/usr/src/sys/FENRIS i386

$ pkg_info | grep ^mysql-
mysql-client-4.0.18 Multithreaded SQL database (client)
mysql-server-4.0.18 Multithreaded SQL database (server)

>Description:

erik at fenris ~$ mysql -u erik -h fenris -p erik_mail
Enter password: 
ERROR 2003: Can't connect to MySQL server on 'fenris' (61)
erik at fenris ~$ 

but "# mysql mysql" works fine

in my mysql data dir, I get a fenris.err file with this being appended
every time I attempt connecting remotely

040213 18:53:11  mysqld started
040213 18:53:12  InnoDB: Started
/usr/local/libexec/mysqld: ready for connections.
Version: '4.0.18'  socket: '/tmp/mysql.sock'  port: 3306
mysqld got signal 11;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.


worked fine before I upgraded the mysql40-(server|client) packages

I tried purging all ports (pkg_delete -a style) and rebuilding to see
if there was a library issue, but the same behavior persists.

if more info is needed, I can try starting the daemon under gdb to get
a backtrace, or whatever... I only have this one fbsd box to test on...

>How-To-Repeat:
update to 4.0.18 and connect via a tcp/ip socket. Both my C application
(using libmysqlclient) and the mysql shell exhibit this behavior.

>Fix:



>Release-Note:
>Audit-Trail:
>Unformatted:



More information about the freebsd-ports-bugs mailing list