Hi, did you do anything to work around it, or are you still sticking at 2.2?
Christoph Am Freitag 08 August 2008 09:37:28 schrieb Stefan Lesicnik: > On Fri, Aug 8, 2008 at 9:27 AM, Christoph Kaulich <[EMAIL PROTECTED]> wrote: > > Hello, > > > > while updating from 2.2.6 tzo 2.3.1 U got: > > > > [EMAIL PROTECTED]:~> ./scripts/DBUpdate-to-2.3.pl > > Start migration of the system... > > > > utf8 "\xFC" does not map to Unicode at /raid/otrs/Kernel/System/Config.pm > > line 161, <$In> chunk 1. > > utf8 "\xFC" does not map to Unicode at /raid/otrs/Kernel/System/Config.pm > > line 161, <$In> chunk 1. > > utf8 "\xF6" does not map to Unicode at /raid/otrs/Kernel/System/Config.pm > > line 161, <$In> chunk 1. > > Malformed UTF-8 character (unexpected non-continuation byte 0x72, > > immediately after start byte 0xfc) in subroutine entry at > > /usr/lib/perl5/5.8.8/x86_64- linux-thread-multi/Data/Dumper.pm line 179. > > Malformed UTF-8 character (unexpected non-continuation byte 0x72, > > immediately after start byte 0xfc) in subroutine entry at > > /usr/lib/perl5/5.8.8/x86_64- linux-thread-multi/Data/Dumper.pm line 179. > > Malformed UTF-8 character (unexpected non-continuation byte 0x6c, > > immediately after start byte 0xfc) in subroutine entry at > > /usr/lib/perl5/5.8.8/x86_64- linux-thread-multi/Data/Dumper.pm line 179. > > Malformed UTF-8 character (unexpected non-continuation byte 0x73, > > immediately after start byte 0xf6) in subroutine entry at > > /usr/lib/perl5/5.8.8/x86_64- linux-thread-multi/Data/Dumper.pm line 179. > > *** glibc detected *** /usr/bin/perl: realloc(): invalid next size: > > 0x0000000002838410 *** > > ======= Backtrace: ========= > > /lib64/libc.so.6[0x2b2bc356221d] > > /lib64/libc.so.6[0x2b2bc35656a8] > > /lib64/libc.so.6(realloc+0x130)[0x2b2bc3566120] > > /usr/bin/perl(Perl_safesysrealloc+0x5c)[0x4715fc] > > /usr/bin/perl(Perl_sv_grow+0x6f)[0x48f76f] > > /usr/bin/perl(Perl_sv_catpvn_flags+0x11f)[0x497a8f] > > /usr/lib/perl5/5.8.8/x86_64-linux-thread- > > multi/auto/Data/Dumper/Dumper.so[0x2b2bc4279ea1] > > /usr/lib/perl5/5.8.8/x86_64-linux-thread- > > multi/auto/Data/Dumper/Dumper.so[0x2b2bc42794a1] > > /usr/lib/perl5/5.8.8/x86_64-linux-thread- > > multi/auto/Data/Dumper/Dumper.so[0x2b2bc4279fe2] > > /usr/lib/perl5/5.8.8/x86_64-linux-thread- > > multi/auto/Data/Dumper/Dumper.so(XS_Data__Dumper_Dumpxs+0xf54)[0x2b2bc427 > >b8c4] /usr/bin/perl(Perl_pp_entersub+0x363)[0x486a53] > > /usr/bin/perl(Perl_runops_debug+0x11e)[0x468e2e] > > /usr/bin/perl(perl_run+0x264)[0x4255f4] > > /usr/bin/perl(main+0xe4)[0x420e54] > > /lib64/libc.so.6(__libc_start_main+0xf4)[0x2b2bc3511b54] > > /usr/bin/perl[0x420cd9] > > > > > > The machine is a Suse 10.3 64bit machine, with perl-5.8.8-76. > > > > Has anyone here a clue, what was going wrong? > > > > Christoph > > > > _______________________________________________ > > OTRS mailing list: otrs - Webpage: http://otrs.org/ > > Archive: http://lists.otrs.org/pipermail/otrs > > To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs > > Support or consulting for your OTRS system? > > => http://www.otrs.com/ > > Hi, > > Sorry I have no solution - but I have exactly the same problem when > upgrading from 2.2.3. > > I had a 2.2.6 instance on the same machine (same perl version etc) > that worked fine... > > It must have something to do with the handling of some of the messages > during the migration... > > Stefan _______________________________________________ OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs Support or consulting for your OTRS system? => http://www.otrs.com/
