Thanks a lot!
Re-installing DBI by force really did the trick.
Lothar
----- Forwarded message from “Ruslan U. Zakirov” cubic@acronis.ru -----
Date: Tue, 13 Jul 2004 14:40:31 +0400
From: “Ruslan U. Zakirov” cubic@acronis.ru
User-Agent: Mozilla/5.0 (X11; U; Linux i686; ru-RU; rv:1.6) Gecko/20040331
X-Accept-Language: ru, en
To: Lothar Fuhlrott dv@proasyl.de
CC: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Re-Logging in / “Attempt to free
unreferencedscalar”]
In-Reply-To: 01e101c468c4$3ab5d3d0$091ba8c0@freiburg
X-Virus-Scanned: by amavisd-milter (http://amavis.org/)In CPAN shell you can use force command.
force test DBI
…
if OK then
force install DBIIn archives there is threads about such problems.
As variant you can rebuild perl with same config, but without old paths
in INC.
use CPAN ‘autobundle’ command to get current module list snapshot.Lothar Fuhlrott wrote:
The question may be dumb, but how do I find out about the old paths? And
what would I have to do to move them to new ones?
I used CPAN to install the modules after upgrading to Perl 5.8.3, and
the
CPAN-snapshot tells me they are all there.Date: Tue, 13 Jul 2004 13:50:23 +0400
From: “Ruslan U. Zakirov” cubic@acronis.ru
User-Agent: Mozilla/5.0 (X11; U; Linux i686; ru-RU; rv:1.6)
Gecko/20040331
X-Accept-Language: ru, en
To: Lothar Fuhlrott dv@proasyl.de
CC: ktm@is.rice.edu, > Subject: Re: Fw: Fw: [rt-users] Re-Logging in
/“Attempt to free unreferencedscalar”
In-Reply-To: 017401c468bd$042d45c0$091ba8c0@freiburg
X-Virus-Scanned: by amavisd-milter (http://amavis.org/)Do you use modules(DBI, DBD…) from old perl paths?
Lothar Fuhlrott wrote:
I did what you told me and installed Apache 1.3.31 with mod_perl 1.29.
There
were no compilation problems. But nothing has changed, the error
messages
are the same as before. Obviously there’s something wrong with my Perl
configuration, but I’m at a loss at finding out what
Here another message in rt.log when I’ve logged out and in again at theweb
interface without shutting my browser down and then try to enter a
menu:
“[warning]: Attempt to free unreferenced scalar: SV 0x968d240 at
/usr/lib/perl5/site_perl/5.8.0/Apache/Session.pm line 616.”
Any idea?
Thanks
Lothar----- Original Message -----
From: “Lothar Fuhlrott” dv@proasyl.de
To: cubic@acronis.ru
Cc: rt-users@lists.bestpractical.com
Sent: Tuesday, July 13, 2004 8:45 AM
Subject: Fw: Fw: [rt-users] Re-Logging in / “Attempt to free
unreferencedscalar”The output of perl -V seems okay to me:
Compile-time options: DEBUGGING MULTIPLICITY USE_ITHREADS
USE_LARGE_FILES
PERL_IMPLICIT_CONTEXT
Built under linux
Compiled at Mar 23 2004 20:56:34
@INC:
/usr/lib/perl5/5.8.3/i386-linux-thread-multi
/usr/lib/perl5/5.8.3
/usr/lib/perl5/site_perl/5.8.3/i386-linux-thread-multi
/usr/lib/perl5/site_perl/5.8.2/i386-linux-thread-multi
/usr/lib/perl5/site_perl/5.8.1/i386-linux-thread-multi
/usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi
/usr/lib/perl5/site_perl/5.8.3
/usr/lib/perl5/site_perl/5.8.2
/usr/lib/perl5/site_perl/5.8.1
/usr/lib/perl5/site_perl/5.8.0
/usr/lib/perl5/site_perl
/usr/lib/perl5/vendor_perl/5.8.3/i386-linux-thread-multi
/usr/lib/perl5/vendor_perl/5.8.2/i386-linux-thread-multi
/usr/lib/perl5/vendor_perl/5.8.1/i386-linux-thread-multi
/usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi
/usr/lib/perl5/vendor_perl/5.8.3
/usr/lib/perl5/vendor_perl/5.8.2
/usr/lib/perl5/vendor_perl/5.8.1
/usr/lib/perl5/vendor_perl/5.8.0
/usr/lib/perl5/vendor_perlI created a 5.8.3-symlink to /usr/bin/perl to avoid any confusion
between
the different versions.
I did not use the Red Hat-mod_perl.rpm, but built the mod_perl-1.99_13
tarball.Date: Mon, 12 Jul 2004 20:00:57 +0400
From: “Ruslan U. Zakirov” cubic@acronis.ru
User-Agent: Mozilla/5.0 (X11; U; Linux i686; ru-RU; rv:1.6)Gecko/20040331
X-Accept-Language: ru, en
To: Lothar Fuhlrott dv@proasyl.de
CC: rt-users@lists.bestpractical.com
Subject: Re: Fw: [rt-users] Re-Logging in / "Attempt to freeunreferenced
scalar"
In-Reply-To: 055801c4681d$ed1d57c0$091ba8c0@freiburg
X-Virus-Scanned: by amavisd-milter (http://amavis.org/)Lothar Fuhlrott wrote:
Well, I believed in the RTWiki lines on Compiling Perl: "mod_perl2
canbe
compiled only as DSO and it’s working fine".
LotharI’m sorry that you were confused with this sentence. It’s all about
DSO
vs static, but not about MP2 stability.IMHO errors comes from perl mainly.
RH9 does have perl5.8.0. Did you rebuild mod_perl after new perl
install? What version of MP2 do you have? If it’s RH9 RPMs then throwit
away, in our days you shouldn’t use anything except 1.99_14 or
higher.perl -V?
Date: Mon, 12 Jul 2004 08:24:24 -0500
From: Kenneth Marshall ktm@is.rice.edu
To: Lothar Fuhlrott dv@proasyl.de
Subject: Re: [rt-users] Re-Logging in / "Attempt to free
unreferencedscalar"
In-Reply-To: 04f401c46810$a72f31f0$091ba8c0@freiburg
User-Agent: Mutt/1.4.2i
X-Virus-Scanned: by amavisd-milter (http://amavis.org/)
X-Virus-Scanned: by amavis-20030314-p2 at is.rice.eduNot to be anti-progress, but isnt’ mod_perl for Apache 2.x still
in beta. I would give it a try with Apache 1.3.31 and mod_perl
1.29.–Ken
Hi out there,
having installed RT 3.2.0 with Red Hat 9 Shrike, Apache
2.0.50/mod_perl2,
Sendmail 8.12.8, Perl 5.8.3 I am still running into problems,
(1) Everytime a web browser “touches” the site, tail -f
/var/log/messages
will produce a whole bunch of messages like this:
Jul 12 13:49:05 salvador RT: Attempt to free unreferenced scalar:
SV
0x96e7c84 at /usr/local/rt/share/html/Elements/Quicksearch line
Jul 12 13:49:05 salvador RT: Attempt to free unreferenced scalar:
SV
0x9637474 at /usr/local/rt/share/html/autohandler line 24.
Jul 12 13:49:07 salvador RT: Attempt to free unreferenced scalar:
SV
0x96e9f20 at /usr/local/rt/share/html/autohandler line 24.
Jul 12 13:49:08 salvador RT: Attempt to free unreferenced scalar:
SV
0x971bea4 at /usr/local/rt/share/html/Elements/SelectMatch line
I don't know if this does any harm, but I'd like to know what itmeans
anyway…
(2) After I have logged out and then in again (same user or not,
no
difference), RT is kicking me out and showing the login screen
everytime I
try to call upon a menu. Only closing down the browser on the
client