Hi Jesse,
I have just removed all content under local/html and also dropped and
reinitialised the database and still see the same error. The only thing
I can think of is it must be a compatibility issue with one of the deps.
I'm checking an autobundle of our perl version 5.8.4 against the
testdeps requirements, one line at a time to try and find the culprit.
Thanks
Rik
Jesse Vincent wrote:
This code has been refactored for 3.6.4. Can you tell me if it still
happens with the RC of 3.6.4? (Which will become the release just as
soon as I get settled at work again.)
Jesse
On Jul 3, 2007, at 10:03 AM, Richard Ellis wrote:
Hi Guys,
I first emailed this one in in May. Full details of the errors etc
are on this archive:
http://www.gossamer-threads.com/lists/rt/users/65651?#65651
An extract is below, but full details of our system etc are on that
thread.
*System error*
*error:* Can't use string ("") as a HASH ref while "strict refs" in
use at /opt/rt3/share/html/Elements/MyRT line 50, <DATA> line 1662.
*context:*
*...*
*46:* <table border="0" width="100%">
*47:* <tr valign="top">
*48:* <td width="70%" class="boxcontainer">
*49:*
*50:* % for my $portlet (@{$portlets->{body}}) {
*51:* <% $show_cb->( $portlet ) %>
*52:* <br />
*53:* % }
*54:*
*...*
*code stack:* /opt/rt3/share/html/Elements/MyRT:50
/opt/rt3/share/html/index.html:79
/opt/rt3/share/html/autohandler:292
raw error <http://gplive.uk:3000/index.html#raw>
Can't use string ("") as a HASH ref while "strict refs" in use at
/opt/rt3/share/html/Elements/MyRT line 50, <DATA> line 1662.
Trace begun at
/usr/local/lib/perl5/site_perl/5.8.4/HTML/Mason/Exceptions.pm line 131
HTML::Mason::Exceptions::rethrow_exception('Can\'t use string ("") as
a HASH ref while "strict refs" in use at
/opt/rt3/share/html/Elements/MyRT line 50, <DATA> line 1662.^J')
called at /opt/rt3/share/html/Elements/MyRT line 50
HTML::Mason::Commands::__ANON__ at
/usr/local/lib/perl5/site_perl/5.8.4/HTML/Mason/Component.pm line 134
HTML::Mason::Component::run('HTML::Mason::Component::FileBased=HASH(0x18b3c20)')
called at /usr/local/lib/perl5/site_perl/5.8.4/HTML/Mason/Request.pm
line 1074
eval {...} at
/usr/local/lib/perl5/site_perl/5.8.4/HTML/Mason/Request.pm line 1068
HTML::Mason::Request::comp(undef, undef) called at
/opt/rt3/share/html/index.html line 79
HTML::Mason::Commands::__ANON__ at
/usr/local/lib/perl5/site_perl/5.8.4/HTML/Mason/Component.pm line 134
HTML::Mason::Component::run('HTML::Mason::Component::FileBased=HASH(0x17bab60)')
called at /usr/local/lib/perl5/site_perl/5.8.4/HTML/Mason/Request.pm
line 1074
eval {...} at
/usr/local/lib/perl5/site_perl/5.8.4/HTML/Mason/Request.pm line 1068
HTML::Mason::Request::comp(undef, undef, undef) called at
/opt/rt3/share/html/autohandler line 292
HTML::Mason::Commands::__ANON__ at
/usr/local/lib/perl5/site_perl/5.8.4/HTML/Mason/Component.pm line 134
HTML::Mason::Component::run('HTML::Mason::Component::FileBased=HASH(0x17e7afc)')
called at /usr/local/lib/perl5/site_perl/5.8.4/HTML/Mason/Request.pm
line 1069
eval {...} at
/usr/local/lib/perl5/site_perl/5.8.4/HTML/Mason/Request.pm line 1068
HTML::Mason::Request::comp(undef, undef, undef) called at
/usr/local/lib/perl5/site_perl/5.8.4/HTML/Mason/Request.pm line 338
eval {...} at
/usr/local/lib/perl5/site_perl/5.8.4/HTML/Mason/Request.pm line 338
eval {...} at
/usr/local/lib/perl5/site_perl/5.8.4/HTML/Mason/Request.pm line 297
HTML::Mason::Request::exec('HTML::Mason::Request::ApacheHandler=HASH(0x1972fa4)')
called at
/usr/local/lib/perl5/site_perl/5.8.4/HTML/Mason/ApacheHandler.pm line
134
eval {...} at
/usr/local/lib/perl5/site_perl/5.8.4/HTML/Mason/ApacheHandler.pm line
134
HTML::Mason::Request::ApacheHandler::exec('HTML::Mason::Request::ApacheHandler=HASH(0x1972fa4)')
called at
/usr/local/lib/perl5/site_perl/5.8.4/HTML/Mason/ApacheHandler.pm line
792
HTML::Mason::ApacheHandler::handle_request('HTML::Mason::ApacheHandler=HASH(0x12c3acc)',
'Apache=SCALAR(0x14cbd54)') called at /opt/rt3/bin/webmux.pl line 123
eval {...} at /opt/rt3/bin/webmux.pl line 123
RT::Mason::handler('Apache=SCALAR(0x14cbd54)') called at /dev/null
line 0
eval {...} at /dev/null line 0
Since then, I have had private emails from 4 people, who are seeing
the same error. It occurred on our kit, when I was upgrading our test
instance from 3.4.6 to 3.6.3.
Everything was fine until after I applied the 3.5.1 patches and
restarted everything. It would appear this isn't unique to our setup.
Does anyone have any ideas how to even begin to find the source of
the bug? I can't take the risk of upgrading our live server until I
can prove this isn't going to screw everything up and I need to
complete migrating our live instance to a new set of hardware soon.
Any ideas anyone?
Thanks
Richard
--
Richard Ellis
.Sun B2B Operations
Sun Microsystems x24727
http://sun.com
_______________________________________________
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
Community help: http://wiki.bestpractical.com
Commercial support: [EMAIL PROTECTED]
Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
_______________________________________________
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
Community help: http://wiki.bestpractical.com
Commercial support: [EMAIL PROTECTED]
Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
