[rt-users] Error: "Use of uninitialized value in subroutine entry at Encode.pm line 190."
Ruslan Zakirov
ruslan.zakirov at gmail.com
Wed Feb 21 14:04:20 EST 2007
Have you tried update of Encode perl module?
On 1/5/07, Alex Moura <alexsm at gmail.com> wrote:
> Hello,
>
> I haven't found information in the Internet and list history about this
> problem and I've decided to ask for your advice.
>
> After a recent upgrade in perl (from 5.8.7 to 5.8.8) and all RT perl
> components of our FreeBSD-6.1 server, we've detected a problem
> where the web interface cannot show a specific ticket history and we
> haven't noticed this problem before.
>
> When we try to access the ticket with the problem, the messages
> recorded in the apache log are:
>
> [Fri Jan 5 09:10:14 2007] [error] [client 200.143.193.21] FastCGI:
> server "/usr/local/rt3/bin/mason_handler.fcgi" stderr: Use
> of uninitialized
> value in subroutine entry at
> /usr/local/lib/perl5/site_perl/5.8.8/mach/Encode.pm line
> 190.
>
> [Fri Jan 5 09:10:25 2007] [warn] FastCGI: server
> "/usr/local/rt3/bin/mason_handler.fcgi" (pid 1871)
> terminated due
> to uncaught signal '11' (Segmentation fault)
>
> And the effect in the web interface is that the ticket history is shown
> incomplete. It shows a few messages of the ticket history and stops
> in the middle of a specific message and doesn't display the rest of
> the history.
>
> To try to solve this problem, today I upgraded RT from
> 3.4.4 to 3.4.5 using the FreeBSD ports, and forced the
> reinstallation of the whole set of required software
> components, including apache and mysql. The error
> meesages above are still the same after this complete
> upgrade.
>
> It seems that the problem appeared after upgrading - in the
> beginning of this week - perl from v.5.8.7 to v.5.8.8, more
> specifically in the file
> /usr/local/lib/perl5/site_perl/5.8.8/mach/Encode.pm.
>
> We would like at least a workaround to recover the ticket
> history content, so we can move on with our work.
>
> We wouldn't bother in opening a new ticket and deleting
> the problematic one after we recover the data we need.
>
> I'd appreciate any tips.
>
> Best regards,
>
> Alex
>
> _______________________________________________
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
>
> Community help: http://wiki.bestpractical.com
> Commercial support: sales at bestpractical.com
>
>
> Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
> Buy a copy at http://rtbook.bestpractical.com
>
--
Best regards, Ruslan.
More information about the rt-users
mailing list