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) 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/DBD/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/40nullsdubious 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:[EMAIL PROTECTED] 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 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/DBD/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/40nullsdubious 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:[EMAIL PROTECTED] 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 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...
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
