Perl_Istack_sp_ptr error

ai_bcn has asked for the wisdom of the Perl Monks concerning the following question:

Hi,

an ubuntu upgrade, from 11.10 to 12.04 LTS (64 bit), affected my Bugzilla 4.2 setup.

I can open and access Bugzilla, and the sanity check completes without any errors. I can search for and find the created tickets, but can't open and can't read them (the page doesn't load, remains hanging), and i can't create new tickets, (the page hangs when i select the "Product" in which i intend to create a new ticket...

MySQL version: 5.5.22

Perl v5.14.2

i'm not sure whether it is a MySQL, Perl or other upgrade effect... but it surprizes me that when i run ./checksetup.pl the identified mysql version is 4..020 when i have installed v 5.5.22, and I get a Perl_Istack_sp_ptr error immediately after that:

root@desk-1:/var/www/bugzilla# ./checksetup.pl
* This is Bugzilla 4.2 on perl 5.14.2
* Running on Linux 3.2.0-24-generic #37-Ubuntu SMP Wed Apr 25 08:43:22 UTC 2012
Checking perl modules...
Checking for CGI.pm (v3.51) ok: found v3.59
Checking for Digest-SHA (any) ok: found v5.71
Checking for TimeDate (v2.21) ok: found v2.24
Checking for DateTime (v0.28) ok: found v0.74
Checking for DateTime-TimeZone (v0.71) ok: found v1.46
Checking for DBI (v1.614) ok: found v1.620
Checking for Template-Toolkit (v2.22) ok: found v2.22
Checking for Email-Send (v2.00) ok: found v2.198
Checking for Email-MIME (v1.904) ok: found v1.910
Checking for URI (v1.37) ok: found v1.60
Checking for List-MoreUtils (v0.22) ok: found v0.33
Checking for Math-Random-ISAAC (v1.0.1) ok: found v1.004
Checking available perl DBD modules...
Checking for DBD-Pg (v1.45) not found
Checking for DBD-mysql (v4.001) ok: found v4.020
/usr/bin/perl: symbol lookup error: lib/x86_64-linux-gnu-thread-multi/auto/DBD/SQLite/SQLite.so: undefined symbol: Perl_Istack_sp_ptr

Reading error related posts and following various directions, i tried to reinstall Perl and CPAN, but this didn't helped. and i ended up in having

/etc/perl
/usr/lib/perl AND
/usr/lib/perl5 (which i'm not sure is ok...)

the /usr/lib/perl directory contains
/..
~5.14
/5.14.2

The perl -v command returns

This is perl 5, version 14, subversion 2 (v5.14.2) built for x86_64-linux-gnu-thread-multi (with 53 registered patches, see perl -V for more detail)

Could you please help ?

Thanks in advance.
Adrian

Comment on Perl_Istack_sp_ptr error

Replies are listed 'Best First'.
Re: Perl_Istack_sp_ptr error by Eliya (Vicar) on May 04, 2012 at 02:35 UTC
`/usr/bin/perl: symbol lookup error: lib/x86_64-linux-gnu-thread-multi/ +auto/DBD/SQLite/SQLite.so: undefined symbol: Perl_Istack_sp_ptr` [download] Looks like your Bugzilla installation has its own DBD::SQLite module¹, and this module had been built with the previous perl (meaning it's binary incompatible with the newer perl). I don't know why your Bugzilla came with its own version of DBD::SQLite instead of using the existing Debian/Ubuntu package, but you might want to try installing the latter package (`sudo apt-get install libdbd-sqlite3-perl`) and see how things go. You probably then also want to ditch/rename the bugzilla-private version to ensure the regular Ubuntu package is in fact being pulled in (for testing purposes, at a minimum, rename both the `SQLite.so` and the `SQLite.pm` files below `./lib/`). it surprizes me that when i run ./checksetup.pl the identified mysql version is 4..020 when i have installed v 5.5.22 The reported 4.020 is the version of the DBD-mysql Perl binding, not of mysql itself. This has nothing to do with the actual, above mentioned, problem. ___ ¹ the installation path of the regular Ubuntu package would be `/usr/lib/perl5/auto/DBD/SQLite/SQLite.so` [download] not `./lib/x86_64-linux-gnu-thread-multi/auto/DBD/SQLite/SQLite.so` [download]	[reply] [d/l] [select]
Re: Perl_Istack_sp_ptr error by bobdabuilda (Beadle) on May 04, 2012 at 00:31 UTC
Hi there, I can't help with your actual problem... but I can help you possibly have more chance of getting an answer from someone who can. Try surrounding your error logs, dir listings etc. with < code > < /code > tags to make it easier to read (easier to distinguish your text from code/examples), and folks will be more inclined to read it. Recently had similar advice given to me, and it does make things better all round :)	[reply]