MySQL upgrade caused Perl coredumps...

I recently upgraded MySQL to version 5.0.4. After the upgrade,
several of my Perl scripts that access the MySQL database began to fail
with "Memory fault coredump" messages. Anyone have any suggestions?
I'm hoping a simple DBI::MySQL upgrade will fix this issue. Here is the
Perl information...

Summary of my perl5 (revision 5 version 8 subversion 7) configuration:
Platform:
osname=3Dhpux, osvers=3D11.11, archname=3DPA-RISC2.0
uname=3D'hp-ux r3 b.11.11 u 9000800 1909236376 unlimited-user =
license
'
config_args=3D'-Dusedevel -Dcc=3Dgcc -Uversiononly
-Dinc_version_list=3Dnone -des'
hint=3Drecommended, useposix=3Dtrue, d_sigaction=3Ddefine
usethreads=3Dundef use5005threads=3Dundef useithreads=3Dundef
usemultiplicity=3Dundef
useperlio=3Ddefine d_sfio=3Dundef uselargefiles=3Ddefine =
usesocks=3Dundef
use64bitint=3Dundef use64bitall=3Dundef uselongdouble=3Dundef
usemymalloc=3Dn, bincompat5005=3Dundef
Compiler:
cc=3D'gcc', ccflags =3D'-mpa-risc-2-0 -D_HPUX_SOURCE -DDEBUGGING
-fno-strict-aliasing -pipe -I/pro/local/include -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=3D64',
optimize=3D'-g -O',
cppflags=3D'-mpa-risc-2-0 -D_HPUX_SOURCE -mpa-risc-2-0 =
-D_HPUX_SOURCE
-DDEBUGGING -fno-strict-aliasing -pipe -I/pro/local/include'
ccversion=3D'', gccversion=3D'3.4.4', gccosandvers=3D'hpux11.11'
intsize=3D4, longsize=3D4, ptrsize=3D4, doublesize=3D8, =
byteorder=3D4321
d_longlong=3Ddefine, longlongsize=3D8, d_longdbl=3Ddefine, =
longdblsize=3D16
ivtype=3D'long', ivsize=3D4, nvtype=3D'double', nvsize=3D8, =
Off_t=3D'off_t',
lseeksize=3D8
alignbytes=3D8, prototype=3Ddefine
Linker and Libraries:
ld=3D'/usr/bin/ld', ldflags =3D'-L/pro/local/lib'
libpth=3D/pro/local/lib /lib /usr/lib /usr/ccs/lib /usr/local/lib
libs=3D-lcl -lpthread -lnsl -lnm -lndbm -lgdbm -ldb -lmalloc -ldld =
-lm
-lcrypt -lsec -lc
perllibs=3D-lcl -lpthread -lnsl -lnm -lmalloc -ldld -lm -lcrypt =
-lsec
-lc
libc=3D/lib/libc.sl, so=3Dsl, useshrplib=3Dfalse, =
libperl=3Dlibperl.a
gnulibc_version=3D''
Dynamic Linking:
dlsrc=3Ddl_hpux.xs, dlext=3Dsl, d_dlsymun=3Dundef, =
ccdlflags=3D'-Wl,-E
-Wl,-B,deferred '
cccdlflags=3D'-fPIC', lddlflags=3D'-b -L/pro/local/lib'


Characteristics of this binary (from libperl):
Compile-time options: DEBUGGING USE_LARGE_FILES
Locally applied patches:
defined-or
Built under hpux
Compiled at Jun 1 2005 13:42:32
@INC:
/opt/perl/lib/5.8.7/PA-RISC2.0
/opt/perl/lib/5.8.7
/opt/perl/lib/site_perl/5.8.7/PA-RISC2.0
/opt/perl/lib/site_perl/5.8.7
/opt/perl/lib/site_perl
.

> Scott Nipp
Sr. Systems Analyst
AT&T Unix Administration
> (214) 858-1289
>=20
For non-emergency HP UNIX work /support requests please open an RM
ticket online at:=20
http://euss.sbc.com or by sending an email
to: "unix sss email "=20
For outage or emergency HP UNIX issues, please refer to the oncall list
at: http://unixsss.sbc.com/oncall/mtsshpwest_oncall.html

Re: MySQL upgrade caused Perl coredumps...

At 10:35 PM -0600 11/3/06, NIPP, SCOTT V \(SBCSI\) wrote:
> I recently upgraded MySQL to version 5.0.4. After the upgrade,
>several of my Perl scripts that access the MySQL database began to fail
>with "Memory fault coredump" messages. Anyone have any suggestions?
>I'm hoping a simple DBI::MySQL upgrade will fix this issue. Here is the
>Perl information...

Before you go about with that, you should move up to a production
release of MySQL, such as 5.0.2x ... MySQL 5.0.4 was an alpha or beta
release, and is well over a year old already. Unless you mistyped
and meant to say 5.0.24.

Also, if you're using MySQL v4.1 or higher, you should be using the
DBD::mysql v3.x series of drivers. If nothing else, because the 2.9x
series will fail to connect due to MySQL user password hashes having
changed in length between 4.0 and 4.1, which affects database users
created after the switch.

-- Darren Duncan

RE: MySQL upgrade caused Perl coredumps...

I'm kind of stuck with the MySQL version here. This is the
pre-built HP version that we are required to use. This is the latest
version available compiled by HP. I am now attempting to build
DBD::MySQL-3.0008 and running into some make test errors. Here is a
sample of the errors.

t/40nulls............/usr/lib/dld.sl: Unresolved symbol: __udivdi3
(code) from
/home/sadmin/sn4265/perl/DBD-mysql-3.0008/blib/arch/auto/DBD /mysql/mysql
..sl
/usr/lib/dld.sl: Unresolved symbol: __umoddi3 (code) from
/home/sadmin/sn4265/perl/DBD-mysql-3.0008/blib/arch/auto/DBD /mysql/mysql
..sl
install_driver(mysql) failed: Can't load
'/home/sadmin/sn4265/perl/DBD-mysql-3.0008/blib/arch/auto/DB D/mysql/mysq
l.sl' for module DBD::mysql: Unresolved external at
/opt/perl/lib/5.8.7/PA-RISC2.0/DynaLoader.pm line 230.
at (eval 1) line 3
Compilation failed in require at (eval 1) line 3.
Perhaps a required shared library or dll isn't installed where expected
at t/40nulls.t line 50
t/40nulls............dubious
Test returned status 215 (wstat 55040, 0xd700)
DIED. FAILED tests 1-11
Failed 11/11 tests, 0.00% okay

I got a lot of these, in fact for just about every test. The
DBD::MySQL module is the only one I am attempting to upgrade. I'm not
sure if I need to update my DBI module or now. One question I have is
how do I check the module versions? Thanks in advance for any
assistance.

-----Original Message-----
From: Darren Duncan [mailto:darren@DarrenDuncan.net]=20
Sent: Saturday, November 04, 2006 3:54 AM
To: dbi-users@perl.org
Subject: Re: MySQL upgrade caused Perl coredumps...


At 10:35 PM -0600 11/3/06, NIPP, SCOTT V \(SBCSI\) wrote:
> I recently upgraded MySQL to version 5.0.4. After the upgrade,
>several of my Perl scripts that access the MySQL database began to fail
>with "Memory fault coredump" messages. Anyone have any suggestions?
>I'm hoping a simple DBI::MySQL upgrade will fix this issue. Here is
the
>Perl information...

Before you go about with that, you should move up to a production=20
release of MySQL, such as 5.0.2x ... MySQL 5.0.4 was an alpha or beta=20
release, and is well over a year old already. Unless you mistyped=20
and meant to say 5.0.24.

Also, if you're using MySQL v4.1 or higher, you should be using the=20
DBD::mysql v3.x series of drivers. If nothing else, because the 2.9x=20
series will fail to connect due to MySQL user password hashes having=20
changed in length between 4.0 and 4.1, which affects database users=20
created after the switch.

-- Darren Duncan

RE: MySQL upgrade caused Perl coredumps...

I just stumbled across something providing a little more
information and not making anything any clearer. Here is the database
related module information...

perl -MDBI -e 'DBI->installed_versions'
Perl : 5.008007 (PA-RISC2.0)
OS : hpux (11.11)
DBI : 1.48
DBD::mysql : 3.0008
DBD::Sponge : 11.10
DBD::Proxy : install_driver(Proxy) failed: Can't locate
RPC/PlClient.pm in @INC
DBD::Oracle : 1.16
DBD::File : 0.33
DBD::ExampleP : 11.12
DBD::DBM : 0.02
DBD::CSV : 0.22

Judging by this I am already running the latest DBD::MySQL,
though I am about 5 versions behind on the DBI module. I hope all of
this helps.

-----Original Message-----
From: NIPP, SCOTT V (SBCSI)=20
Sent: Saturday, November 04, 2006 12:02 PM
To: 'Darren Duncan'; dbi-users@perl.org
Subject: RE: MySQL upgrade caused Perl coredumps...


I'm kind of stuck with the MySQL version here. This is the
pre-built HP version that we are required to use. This is the latest
version available compiled by HP. I am now attempting to build
DBD::MySQL-3.0008 and running into some make test errors. Here is a
sample of the errors.

t/40nulls............/usr/lib/dld.sl: Unresolved symbol: __udivdi3
(code) from
/home/sadmin/sn4265/perl/DBD-mysql-3.0008/blib/arch/auto/DBD /mysql/mysql
..sl
/usr/lib/dld.sl: Unresolved symbol: __umoddi3 (code) from
/home/sadmin/sn4265/perl/DBD-mysql-3.0008/blib/arch/auto/DBD /mysql/mysql
..sl
install_driver(mysql) failed: Can't load
'/home/sadmin/sn4265/perl/DBD-mysql-3.0008/blib/arch/auto/DB D/mysql/mysq
l.sl' for module DBD::mysql: Unresolved external at
/opt/perl/lib/5.8.7/PA-RISC2.0/DynaLoader.pm line 230.
at (eval 1) line 3
Compilation failed in require at (eval 1) line 3.
Perhaps a required shared library or dll isn't installed where expected
at t/40nulls.t line 50
t/40nulls............dubious
Test returned status 215 (wstat 55040, 0xd700)
DIED. FAILED tests 1-11
Failed 11/11 tests, 0.00% okay

I got a lot of these, in fact for just about every test. The
DBD::MySQL module is the only one I am attempting to upgrade. I'm not
sure if I need to update my DBI module or now. One question I have is
how do I check the module versions? Thanks in advance for any
assistance.

-----Original Message-----
From: Darren Duncan [mailto:darren@DarrenDuncan.net]=20
Sent: Saturday, November 04, 2006 3:54 AM
To: dbi-users@perl.org
Subject: Re: MySQL upgrade caused Perl coredumps...


At 10:35 PM -0600 11/3/06, NIPP, SCOTT V \(SBCSI\) wrote:
> I recently upgraded MySQL to version 5.0.4. After the upgrade,
>several of my Perl scripts that access the MySQL database began to fail
>with "Memory fault coredump" messages. Anyone have any suggestions?
>I'm hoping a simple DBI::MySQL upgrade will fix this issue. Here is
the
>Perl information...

Before you go about with that, you should move up to a production=20
release of MySQL, such as 5.0.2x ... MySQL 5.0.4 was an alpha or beta=20
release, and is well over a year old already. Unless you mistyped=20
and meant to say 5.0.24.

Also, if you're using MySQL v4.1 or higher, you should be using the=20
DBD::mysql v3.x series of drivers. If nothing else, because the 2.9x=20
series will fail to connect due to MySQL user password hashes having=20
changed in length between 4.0 and 4.1, which affects database users=20
created after the switch.

-- Darren Duncan