From owner-freebsd-questions Fri Jan 19 3:35: 2 2001 Delivered-To: freebsd-questions@freebsd.org Received: from mohegan.mohawk.net (mohegan.mohawk.net [63.66.68.21]) by hub.freebsd.org (Postfix) with ESMTP id 5BE1837B400 for ; Fri, 19 Jan 2001 03:34:44 -0800 (PST) Received: from mohegan.mohawk.net (mohegan.mohawk.net [63.66.68.21]) by mohegan.mohawk.net (8.9.3/8.9.3) with ESMTP id GAA91430 for ; Fri, 19 Jan 2001 06:40:06 -0500 (EST) (envelope-from rjh@mohawk.net) Date: Fri, 19 Jan 2001 06:40:06 -0500 (EST) From: Ralph Huntington To: questions@freebsd.org Subject: perl-mysql weirdness Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Running FreeBSD 4.2-RELEASE, I wonder if anyone else has encountered this phenomenon? Loading MySQL via sysinstall, I selected version 3.23.26 of the server and client. I also selected p5-Mysql-modules-1.2215 because I needed the DBD module in it. p5-Mysql-modules has a dependency on mysql-client but insists (from sysinstall anyway) on selecting the older client 3.22.32 which ends up overwriting the newer one I had chosen, although I did not notice that at the time. The result was to have perl dumping core when anyone attempted to access a mysql database from a perl-based interface. Command-line access seemed to be okay, but any time someone came in from mysqlman (for example), perl dumped core with a signal 11! We spent some time looking for a hardware problem (signal 11 after all) but it turned out to be the conflicting mysql client. I solved the problem by uninstalling mysql client and server as well as the p5-Mysql-modules. I replaced the p5-Mysql-modules from CPAN and then went back to sysinstall to get the latest mysql server and client packages. Voila, everything okay now. -=ralph=- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message