[otrs] UTF-8 problem, but only in Preview (L) mode
I've recently (first of the year) upgraded from 2.4 to 3.3.3 (taking all intermediate steps, etc... including DB conversion to UTF-8) I'm running on Ubuntu 13.10 and Postgresql 9.1.11. I've spent most of the day googling and testing; I'm aware that these UTF problems are brought about by Perl, specifically the Encode module, not necessarily OTRS itself. But none of my research has found a problem with these exact symptoms, and I'm not sure how to proceed. SYMPTOM is "Internal Server Error" message from apache. LOGGED ERROR from apache (2.4.x) is: * Wed Jan 08 18:31:46.889492 2014] [:error] [pid 5613] Malformed UTF-8 character (fatal) at /opt/otrs//Kernel/Output/HTML/OutputFilterTextURL.pm line 42. STEPS TO REPRODUCE: This occurs ONLY if the list is viewed in "L" mode (URL parameter "View=Preview"). I can play with the "StartHit=" URL parameter to identify the offending message. The message displays just fine when Zoomed, and I see no odd characters; however, there are PDFattachments. So, while all the errors and tracing I can do point back to Perl and Kernel/Output/HTML modules, etc... I can't see why the "L" display gets a fatal error and the Ticket Zoom display, even when displaying all articles, does not. Seems like there has to be a clue in there, but it eludes me... The UTF-8 issues are widespread, so feel free to point me at a useful resource if this is a faq or something, despite my fruitless searches :-) TIA, MikeM - 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
[otrs] utf-8 errors trying to upgrade to 2.4.2
Hello, colleagues I'm trying to upgrade my 2.3.3 (with ITSM) to 2.4.2. I'm following the steps in UPGRADING file. DB restore and DB update went fine. running scripts/DBUpdate-to-2.4.pl gives me: o...@2078 /var/www/some_dir/otrs-2.4.2 $ scripts/DBUpdate-to-2.4.pl Start migration of the system... utf8 "\xF6" does not map to Unicode at /var/www/some_dir/otrs-2.4.2/Kernel/System/Config.pm line 161, <$In> chunk 1. utf8 "\xFC" does not map to Unicode at /var/www/some_dir/otrs-2.4.2/Kernel/System/Config.pm line 161, <$In> chunk 1. utf8 "\xFC" does not map to Unicode at /var/www/some_dir/otrs-2.4.2/Kernel/System/Config.pm line 161, <$In> chunk 1. ... a lot more lines skipped Malformed UTF-8 character (unexpected non-continuation byte 0x6e, immediately after start byte 0xf6) in subroutine entry at /usr/lib/perl5/5.8.8/i686-linux-thread-multi/Data/Dumper.pm line 179. *** glibc detected *** /usr/bin/perl: munmap_chunk(): invalid pointer: 0x099ae250 *** === Backtrace: = /lib/libc.so.6[0xd566d0] /usr/bin/perl(Perl_safesysfree+0x21)[0x80b5ed1] /usr/bin/perl[0x80be3a2] /usr/bin/perl(Perl_hv_free_ent+0x65)[0x80be755] /usr/bin/perl[0x80be8d8] /usr/bin/perl(Perl_hv_undef+0x34)[0x80c0854] /usr/bin/perl(Perl_sv_clear+0x5a4)[0x80d2d94] /usr/bin/perl(Perl_sv_free+0x83)[0x80d30e3] /usr/bin/perl(Perl_sv_clear+0x3b1)[0x80d2ba1] /usr/bin/perl(Perl_sv_free+0x83)[0x80d30e3] /usr/bin/perl(Perl_hv_free_ent+0x47)[0x80be737] /usr/bin/perl[0x80be8d8] /usr/bin/perl(Perl_hv_undef+0x34)[0x80c0854] /usr/bin/perl(Perl_sv_clear+0x5a4)[0x80d2d94] /usr/bin/perl(Perl_sv_free+0x83)[0x80d30e3] /usr/bin/perl(Perl_sv_clear+0x3b1)[0x80d2ba1] /usr/bin/perl(Perl_sv_free+0x83)[0x80d30e3] /usr/bin/perl(Perl_free_tmps+0x62)[0x80f37a2] /usr/bin/perl(Perl_pp_nextstate+0x54)[0x80c6184] /usr/bin/perl(Perl_runops_standard+0x29)[0x80c40d9] /usr/bin/perl(perl_run+0x12b)[0x8067a9b] /usr/bin/perl(main+0x13e)[0x8063bce] /lib/libc.so.6(__libc_start_main+0xdc)[0xd026fc] /usr/bin/perl[0x8063a01] === Memory map: 0011-00119000 r-xp 08:04 32866356 /usr/lib/perl5/vendor_perl/5.8.8/i686-linux-thread-multi/auto/List/Util/Util.so 00119000-0011a000 r--p 8000 08:04 32866356 /usr/lib/perl5/vendor_perl/5.8.8/i686-linux-thread-multi/auto/List/Util/Util.so 0011a000-0011b000 rw-p 9000 08:04 32866356 /usr/lib/perl5/vendor_perl/5.8.8/i686-linux-thread-multi/auto/List/Util/Util.so 0011b000-00122000 r-xp 08:04 25788468 /usr/lib/perl5/5.8.8/i686-linux-thread-multi/auto/Data/Dumper/Dumper.so 00122000-00123000 r--p 6000 08:04 25788468 /usr/lib/perl5/5.8.8/i686-linux-thread-multi/auto/Data/Dumper/Dumper.so 00123000-00124000 rw-p 7000 08:04 25788468 /usr/lib/perl5/5.8.8/i686-linux-thread-multi/auto/Data/Dumper/Dumper.so 00124000-00129000 r-xp 08:04 25953538 /usr/lib/perl5/vendor_perl/5.8.8/i686-linux-thread-multi/auto/Sys/Syslog/Syslog.so 00129000-0012a000 r--p 4000 08:04 25953538 /usr/lib/perl5/vendor_perl/5.8.8/i686-linux-thread-multi/auto/Sys/Syslog/Syslog.so 0012a000-0012b000 rw-p 5000 08:04 25953538 /usr/lib/perl5/vendor_perl/5.8.8/i686-linux-thread-multi/auto/Sys/Syslog/Syslog.so 0012b000-0016c000 r-xp 08:04 22237305 /usr/lib/libssl.so.0.9.8 0016c000-0016d000 r--p 0004 08:04 22237305 /usr/lib/libssl.so.0.9.8 0016d000-0017 rw-p 00041000 08:04 22237305 /usr/lib/libssl.so.0.9.8 0017-00179000 r-xp 08:04 27086098 /lib/libnss_files-2.9.so 00179000-0017a000 r--p 8000 08:04 27086098 /lib/libnss_files-2.9.so 0017a000-0017b000 rw-p 9000 08:04 27086098 /lib/libnss_files-2.9.so 00185000-00188000 r-xp 08:04 26067089 /usr/lib/perl5/5.8.8/i686-linux-thread-multi/auto/Fcntl/Fcntl.so 00188000-00189000 r--p 2000 08:04 26067089 /usr/lib/perl5/5.8.8/i686-linux-thread-multi/auto/Fcntl/Fcntl.so 00189000-0018a000 rw-p 3000 08:04 26067089 /usr/lib/perl5/5.8.8/i686-linux-thread-multi/auto/Fcntl/Fcntl.so 0018a000-00194000 r-xp 08:04 22237920 /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/libgcc_s.so.1 00194000-00195000 r--p 9000 08:04 22237920 /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/libgcc_s.so.1 00195000-00196000 rw-p a000 08:04 22237920 /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/libgcc_s.so.1 0022b000-0022d000 r-xp 08:04 27085641 /lib/libutil-2.9.so 0022d000-0022e000 r--p 1000 08:04 27085641 /lib/libutil-2.9.so 0022e000-0022f000 rw-p 2000 08:04 27085641 /lib/libutil-2.9.so 002f2000-002fa000 r-xp 08:04 25919509 /usr/lib/perl5/5.8.8/i686-linux-thread-multi/auto/Encode/Encode.so 002fa000-002fb000 r--p 7000 08:04 25919509 /usr/lib/perl5/5.8.8/i686-linux-thread-multi/auto/Encode/Encode.so 002fb000-002fc000 rw-p 8000 08:04 25919509 /usr/lib/perl5/5.8.8/i686-linux-thread-multi/auto/Encode/Encode.so 002fc000-00416000 r-xp 08:04 23986217 /usr/lib/mysql/libmysqlclient.so.15.0.0 00416000-00418000 r--p 00119000 08:04 23986217 /usr/lib/mysql/libmysqlclient.so.15.0.0 00418000-004
Re: [otrs] UTF-8 breaks 2.3.4 SysConfig interface
Dear list,
I´m aware that this thread is a couple of months old but I just ran into the
very same issue, after changing the default charset. I also found the
solution... the issue here was that the sysconfig cache files are in a
different charset from what OTRS expects.
The error messages I found in the Apache error log were
[Sat Jul 11 13:11:48 2009] -e: utf8 "\xFC" does not map to Unicode at
/opt/otrs//Kernel/System/Config.pm line 161, <$In> chunk 1.
[Sat Jul 11 13:11:49 2009] -e: utf8 "\xE4" does not map to Unicode at
/opt/otrs//Kernel/System/Config.pm line 161, <$In> chunk 1.
[Sat Jul 11 13:11:54 2009] -e: utf8 "\xFC" does not map to Unicode at
/opt/otrs//Kernel/System/Config.pm line 161, <$In> chunk 1.
[Sat Jul 11 13:11:54 2009] -e: utf8 "\xE4" does not map to Unicode at
/opt/otrs//Kernel/System/Config.pm line 161, <$In> chunk 1.
If you just delete the cache files OTRS will create new ones and you´d be
good to go...
By default the files are in /opt/otrs/var/tmp and their name starts with
SysConfig-Cache
mich...@kid:/opt/otrs/var/tmp$ ls -l
total 1828
drwxrwsr-x 3 www-data nogroup4096 2009-07-10 10:28 Cache
-rw-rw-r-- 1 www-data nogroup 671010 2009-07-10 10:28
SysConfig-Cache_Kernel_Conig_Files_Framework.xml-1aec9a47e59a99c0f63cfe9c578a58bb.pm
-rw-rw-r-- 1 www-data nogroup4483 2009-07-10 10:28
SysConfig-Cache_Kernel_Config_Files_Support.xml-5aa644823bdb01b11c6d198f84ca9f91.pm
-rw-rw-r-- 1 www-data nogroup 1179396 2009-07-10 10:28
SysConfig-Cache_Kernel_Config_Files_Ticket.xml-f8689fe4f54650acc42b34d49678f10a.pm
I guess if Config.pm would check if the cache files are valid, and would
delete them if they aren´t, that would make the system able to fix this
issue itself.
Kindest regards,
--
Michiel Beijen
Software Consultant
+31 6 - 457 42 418
Bee Free IT + http://beefreeit.nl
On Mon, Mar 2, 2009 at 05:51, Afshar Mohebbi wrote:
> Hi,
>
> We have have a same problem but in IIS. We are using OTRS in a none-Europe
> alphabet and can't ignore utf-8.
>
> Afshar
>
>
> On Mon, Mar 2, 2009 at 4:21 AM, Paul wrote:
>
>> Hi all,
>>
>> I upgraded OTRS 2.3.3 to 2.3.4 and found that when $Self->{DefaultCharset}
>> is set to 'utf-8', the SysConfig area of the Admin interface results in a
>> 500 server error. Apache error logs show the following:
>>
>> [Sun Mar 01 17:45:56 2009] [error] [client xxx.xxx.xxx.xxx] [Sun Mar 1
>> 18:45:56 2009] index.pl: utf8 "\\xF6" does not map to Unicode at
>> ../..//Kernel/System/Config.pm line 161, <$In> chunk 1., referer:
>> https://otrs.host/path/index.pl?Action=Admin
>> [Sun Mar 01 17:45:56 2009] [error] [client xxx.xxx.xxx.xxx] [Sun Mar 1
>> 18:45:56 2009] index.pl: utf8 "\\xFC" does not map to Unicode at
>> ../..//Kernel/System/Config.pm line 161, <$In> chunk 1., referer:
>> https://otrs.host/path/index.pl?Action=Admin
>> [Sun Mar 01 17:45:57 2009] [error] [client xxx.xxx.xxx.xxx] [Sun Mar 1
>> 18:45:57 2009] index.pl: utf8 "\\xE4" does not map to Unicode at
>> ../..//Kernel/System/Config.pm line 161, <$In> chunk 1., referer:
>> https://otrs.host/path/index.pl?Action=Admin
>> [Sun Mar 01 17:45:58 2009] [error] [client xxx.xxx.xxx.xxx] [Sun Mar 1
>> 18:45:58 2009] index.pl: utf8 "\\xFC" does not map to Unicode at
>> ../..//Kernel/System/Config.pm line 161, <$In> chunk 1., referer:
>> https://otrs.host/path/index.pl?Action=Admin
>> [Sun Mar 01 17:45:58 2009] [error] [client xxx.xxx.xxx.xxx] [Sun Mar 1
>> 18:45:58 2009] index.pl: Malformed UTF-8 character (unexpected
>> non-continuation byte 0x67, immediately after start byte 0xfc) in
>> subroutine
>> entry at /usr/lib/perl/5.8/Data/Dumper.pm line 179., referer:
>> https://otrs.host/path/index.pl?Action=Admin
>> [Sun Mar 01 17:45:58 2009] [error] [client xxx.xxx.xxx.xxx] *** glibc
>> detected *** free(): invalid next size (normal): 0x095c6590 ***, referer:
>> https://otrs.host/path/index.pl?Action=Admin
>> [Sun Mar 01 17:45:58 2009] [error] [client xxx.xxx.xxx.xxx] Premature end
>> of
>> script headers: index.pl, referer:
>> https://otrs.host/path/index.pl?Action=Admin
>>
>> Changing the default charset to iso-8859-1 the problem goes away. Any
>> ideas?
>> We need UTF-8. Reverting to 2.3.3 resolves the issue as well with utf-8.
>>
>> Best wishes,
>> Paul
>>
>> -
>> 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
>>
>> NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
>> http://www.otrs.com/en/support/enterprise-subscription/
>>
>
>
> -
> 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
>
> NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
> http://www.otrs.com/en/support/enterprise-subscription/
>
--
Re: [otrs] UTF-8 breaks 2.3.4 SysConfig interface
Hi,
We have have a same problem but in IIS. We are using OTRS in a none-Europe
alphabet and can't ignore utf-8.
Afshar
On Mon, Mar 2, 2009 at 4:21 AM, Paul wrote:
> Hi all,
>
> I upgraded OTRS 2.3.3 to 2.3.4 and found that when $Self->{DefaultCharset}
> is set to 'utf-8', the SysConfig area of the Admin interface results in a
> 500 server error. Apache error logs show the following:
>
> [Sun Mar 01 17:45:56 2009] [error] [client xxx.xxx.xxx.xxx] [Sun Mar 1
> 18:45:56 2009] index.pl: utf8 "\\xF6" does not map to Unicode at
> ../..//Kernel/System/Config.pm line 161, <$In> chunk 1., referer:
> https://otrs.host/path/index.pl?Action=Admin
> [Sun Mar 01 17:45:56 2009] [error] [client xxx.xxx.xxx.xxx] [Sun Mar 1
> 18:45:56 2009] index.pl: utf8 "\\xFC" does not map to Unicode at
> ../..//Kernel/System/Config.pm line 161, <$In> chunk 1., referer:
> https://otrs.host/path/index.pl?Action=Admin
> [Sun Mar 01 17:45:57 2009] [error] [client xxx.xxx.xxx.xxx] [Sun Mar 1
> 18:45:57 2009] index.pl: utf8 "\\xE4" does not map to Unicode at
> ../..//Kernel/System/Config.pm line 161, <$In> chunk 1., referer:
> https://otrs.host/path/index.pl?Action=Admin
> [Sun Mar 01 17:45:58 2009] [error] [client xxx.xxx.xxx.xxx] [Sun Mar 1
> 18:45:58 2009] index.pl: utf8 "\\xFC" does not map to Unicode at
> ../..//Kernel/System/Config.pm line 161, <$In> chunk 1., referer:
> https://otrs.host/path/index.pl?Action=Admin
> [Sun Mar 01 17:45:58 2009] [error] [client xxx.xxx.xxx.xxx] [Sun Mar 1
> 18:45:58 2009] index.pl: Malformed UTF-8 character (unexpected
> non-continuation byte 0x67, immediately after start byte 0xfc) in
> subroutine
> entry at /usr/lib/perl/5.8/Data/Dumper.pm line 179., referer:
> https://otrs.host/path/index.pl?Action=Admin
> [Sun Mar 01 17:45:58 2009] [error] [client xxx.xxx.xxx.xxx] *** glibc
> detected *** free(): invalid next size (normal): 0x095c6590 ***, referer:
> https://otrs.host/path/index.pl?Action=Admin
> [Sun Mar 01 17:45:58 2009] [error] [client xxx.xxx.xxx.xxx] Premature end
> of
> script headers: index.pl, referer:
> https://otrs.host/path/index.pl?Action=Admin
>
> Changing the default charset to iso-8859-1 the problem goes away. Any
> ideas?
> We need UTF-8. Reverting to 2.3.3 resolves the issue as well with utf-8.
>
> Best wishes,
> Paul
>
> -
> 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
>
> NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
> http://www.otrs.com/en/support/enterprise-subscription/
>
-
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
NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/
[otrs] UTF-8 breaks 2.3.4 SysConfig interface
Hi all,
I upgraded OTRS 2.3.3 to 2.3.4 and found that when $Self->{DefaultCharset}
is set to 'utf-8', the SysConfig area of the Admin interface results in a
500 server error. Apache error logs show the following:
[Sun Mar 01 17:45:56 2009] [error] [client xxx.xxx.xxx.xxx] [Sun Mar 1
18:45:56 2009] index.pl: utf8 "\\xF6" does not map to Unicode at
../..//Kernel/System/Config.pm line 161, <$In> chunk 1., referer:
https://otrs.host/path/index.pl?Action=Admin
[Sun Mar 01 17:45:56 2009] [error] [client xxx.xxx.xxx.xxx] [Sun Mar 1
18:45:56 2009] index.pl: utf8 "\\xFC" does not map to Unicode at
../..//Kernel/System/Config.pm line 161, <$In> chunk 1., referer:
https://otrs.host/path/index.pl?Action=Admin
[Sun Mar 01 17:45:57 2009] [error] [client xxx.xxx.xxx.xxx] [Sun Mar 1
18:45:57 2009] index.pl: utf8 "\\xE4" does not map to Unicode at
../..//Kernel/System/Config.pm line 161, <$In> chunk 1., referer:
https://otrs.host/path/index.pl?Action=Admin
[Sun Mar 01 17:45:58 2009] [error] [client xxx.xxx.xxx.xxx] [Sun Mar 1
18:45:58 2009] index.pl: utf8 "\\xFC" does not map to Unicode at
../..//Kernel/System/Config.pm line 161, <$In> chunk 1., referer:
https://otrs.host/path/index.pl?Action=Admin
[Sun Mar 01 17:45:58 2009] [error] [client xxx.xxx.xxx.xxx] [Sun Mar 1
18:45:58 2009] index.pl: Malformed UTF-8 character (unexpected
non-continuation byte 0x67, immediately after start byte 0xfc) in subroutine
entry at /usr/lib/perl/5.8/Data/Dumper.pm line 179., referer:
https://otrs.host/path/index.pl?Action=Admin
[Sun Mar 01 17:45:58 2009] [error] [client xxx.xxx.xxx.xxx] *** glibc
detected *** free(): invalid next size (normal): 0x095c6590 ***, referer:
https://otrs.host/path/index.pl?Action=Admin
[Sun Mar 01 17:45:58 2009] [error] [client xxx.xxx.xxx.xxx] Premature end of
script headers: index.pl, referer:
https://otrs.host/path/index.pl?Action=Admin
Changing the default charset to iso-8859-1 the problem goes away. Any ideas?
We need UTF-8. Reverting to 2.3.3 resolves the issue as well with utf-8.
Best wishes,
Paul
-
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
NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/
[otrs] UTF-8 and StdAttachment
Hi,
since we changed the DefaultCharset in Kernel/Config.pm from
$Self->{'DefaultCharset'} = 'iso-8859-1';
to
$Self->{'DefaultCharset'} = 'utf-8';
we got trouble with StdAttachments. The DefaultCharset of our MySQL
database is from first day utf-8 (also while iso-8859-1 is the
DefaultCharset in OTRS). A sended answer with a StdAttachment have the
double size than it really is. For sure, after receiving the
Agent-Response-Mail with the standard attachment, it can't be opened.
When we load a new standard attachment to otrs after switching to utf-8
DefaultCharset and use this new standard attachment, the same thing
happen. It makes no difference.
The table standard_attachment is set to collation utf8_general_ci for
fields name, content_type, filename, comments. All other fields aren't
affected by collations. The content field also has the binary attribute
flag.
When we shortly switch bag to iso, the standard attachment have the
right size and could be read very well on client side.
It looks like, that only database stored attachments are affected by
this issue because uploading an attachment while composing an agent
response article, the attachment could be read very well on client side.
Before I forgot: we're using OTRS 2.2.2. I know, there is OTRS 2.2.4,
but I couldn't find any related documented change in logs.
Bye
Daniel
___
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/
[otrs] UTF-8 problems
Help needed. I try to set OTRS 2.0.4 in UTF-8. I have set UTF-8 for DefaultCharset . When I set LogModule: to SysLog and LogModule::SysLog::Charset: to UTF-8 there is problem to fetch emails with popMasterpop3.pl : Can't create PID PostMasterPOP3, because it's already running and after popMasterpop3.pl -f 1 : Wide character in syswrite at /usr/lib/perl/5.8/Sys/Syslog.pm line 765 When I set LogModule: to File emails are fetched but afterthat there is incoming next email: Cron <[EMAIL PROTECTED]> test -x $HOME/bin/PostMasterPOP3.pl && $HOME/bin/PostMasterPOP[..] Wide character in print at /usr/share/otrs/Kernel/System/Log/File.pm line 60. Above situations tested when sending, to account form which OTRS is fetching emails, emails with special chars in subject and body, for example polish chars like ŻŹĆŃŁĄŚÓżźćńłąśęół. Besides when sending emails with such characters like above or reciving such emails, in system log avaible at OTRS web , this characters when wrote in subjcet are not readable and log at web looks like this: New Ticket [20070327117/Fw: ÃÂÃÂÃÂàÃÂÃÂÃÂûÃÂÃÂÃÂàÃÂÃÂÃÂùÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂàÃÂÃÂÃÂÃÂÃÂÃÂÃÂàÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂàÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂàÃÂÃÂÃÂüÃÂÃÂÃÂàÃÂÃÂÃÂú] created (TicketID=209,Queue=Postmaster,Priority=3 normal,State=new) Similar it looks subject in Outlook Express (unreadable) but in window where is list of emails subject there is ok but in main email windows subject is unreadable. Body is readable. What user can do about it? Switch to other encoding then UTF-8 in log encoding ? End of transmission ___ 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 orr consulting for your OTRS system? => http://www.otrs.com/
[otrs] utf-8/unicode problems
Hi, After many problems, I have finally been able to setup OTRS with UTF-8 as the DefaultCharset. I originally installed OTRS without unicode support and with perl5.6 and that cause problems when I moved to unicode because the database was in SQL_ASCII. This is all fixed now (perl 5.8, unicode in the database, DefaultCharset=utf-8), but now I'm seeing problems in the mails sent by OTRS. The notifications are sent in the ISO-8859-15 encoding, which is causing obvious problems because the content of the email is actually unicode. Also, the responses sent to customers is sent with unicode headers, but doesn't show up properly in Thunderbird, even though thunderbird thinks the mail is indeed unicode. The first attached message is a typical autoresponse and has a iso-8859-15 encoding. The second attached message is a response done by an agent and has the following encoding: Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: 8bit Any help would be appreciated because right now all responses from my agents go out corrupted. A. --- Begin Message --- Ceci est une réponse automatisée du systÚme de support technique du Réseau Koumbit. Un nouveau ticket (# 200604201096) a été créé pour assurer le suivi de votre requête. Votre demande sera examinée par un de nos technicien, qui y répondra dans les plus brefs délais. Merci, Le Réseau Koumbit 1-514-387-6262 http://koumbit.org/ - This is an automated response from the Koumbit tech support system. A new ticket (#1479) has been created for the followup of your request. Your request has been transmitted to our team. We will respond as soon as possible. Thank you, Le Réseau Koumbit 1-514-387-6262 http://koumbit.org/ The Anarcat <[EMAIL PROTECTED]> wrote: > nouveau test autorépondeur --- End Message --- --- Begin Message --- The Anarcat, Merci d'avoir envoyé votre requête. Je fais un test de réponse voir si les accents sortent ok. A. The Anarcat <[EMAIL PROTECTED]> écrit: > oups, oublié de ficher ça ici. il s'agit ici de garder le suivi du > problème de l'autorespondeur qui fucke les accents parce qu'il encode > les mails en iso8859-15: > > http://wiki.koumbit.net/OpenTicketRequestSystem/EncodingIssues > > A. > Merci, -- Antoine Beaupré Ãquipe de support technique de Koumbit [EMAIL PROTECTED] | Web: http://koumbit.org/ | 514-387-6262 --- End Message --- ___ 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 oder Consulting für Ihr OTRS System? => http://www.otrs.de/
Re: [otrs] utf-8 error
hmmm, then keep on taking your time, it seems it is really helpful ;) thanks ibrahim --- [EMAIL PROTECTED] wrote: > hmmm, > > if i take my time and put "wide character in > sysswrite" into google than > im told that this is > a perl error of multibyte utf-8 support wellknown in > CPan.. > > may be you take your time and search in the > appropriate mailing list? > > Li > > > [EMAIL PROTECTED] schrieb am 16.02.2006 > 11:38:48: > > > Hi All, > > > > I wanted to repeat my question, isnt there someone > > who had this error and find a solution :( > > > > When I configured OTRS for 'utf-8' support and use > > some Cyrillian characters in creating a new ticket > I > > got an > > error saying: > > > > "Wide character in syswrite at > > C:/OTRS/Perl/lib/Net/Cmd.pm line 436." > > > > But the system still creates the ticket.. > > What is wrong, what did I do wrong? I hope someone > can > > help me? > > > > Thanks for your time, > > > > Best Regards, > > ibrahim > > > > __ > > Do You Yahoo!? > > Tired of spam? Yahoo! Mail has the best spam > protection around > > http://mail.yahoo.com > > ___ > > 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 oder Consulting für Ihr OTRS System? > > => http://www.otrs.de/ > > ___ > 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 oder Consulting für Ihr OTRS System? > => http://www.otrs.de/ __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ 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 oder Consulting für Ihr OTRS System? => http://www.otrs.de/
Re: [otrs] utf-8 error
hmmm, if i take my time and put "wide character in sysswrite" into google than im told that this is a perl error of multibyte utf-8 support wellknown in CPan.. may be you take your time and search in the appropriate mailing list? Li [EMAIL PROTECTED] schrieb am 16.02.2006 11:38:48: > Hi All, > > I wanted to repeat my question, isnt there someone > who had this error and find a solution :( > > When I configured OTRS for 'utf-8' support and use > some Cyrillian characters in creating a new ticket I > got an > error saying: > > "Wide character in syswrite at > C:/OTRS/Perl/lib/Net/Cmd.pm line 436." > > But the system still creates the ticket.. > What is wrong, what did I do wrong? I hope someone can > help me? > > Thanks for your time, > > Best Regards, > ibrahim > > __ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > ___ > 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 oder Consulting für Ihr OTRS System? > => http://www.otrs.de/ ___ 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 oder Consulting für Ihr OTRS System? => http://www.otrs.de/
[otrs] utf-8 error
Hi All, I wanted to repeat my question, isnt there someone who had this error and find a solution :( When I configured OTRS for 'utf-8' support and use some Cyrillian characters in creating a new ticket I got an error saying: "Wide character in syswrite at C:/OTRS/Perl/lib/Net/Cmd.pm line 436." But the system still creates the ticket.. What is wrong, what did I do wrong? I hope someone can help me? Thanks for your time, Best Regards, ibrahim __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ 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 oder Consulting für Ihr OTRS System? => http://www.otrs.de/
[otrs] utf-8
Hi All, When I configured OTRS for 'utf-8' support and use some Cyrillian characters in creating a new ticket I got an error saying: "Wide character in syswrite at C:/OTRS/Perl/lib/Net/Cmd.pm line 436." But the system still creates the ticket.. What is wrong, what did I do wrong? I hope someone can help me? Thanks for your time, Best Regards, ibrahim __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ 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 oder Consulting für Ihr OTRS System? => http://www.otrs.de/
[otrs] utf-8 problem
Hello, i've installed yesterday Otrs to RedHat Enterprise 3 edition and got problems with UTF-8 i cannot login into the program in error log i see error: [Tue Nov 08 07:15:28 2005] [error] 27724: ModPerl::Registry: Usage: Apache::RequestRec::BINMODE(r) at /opt/otrs//Kernel/System /Encode.pm line 224, line 8.! in apache i've setted defaultencoding to utf-8 Please help. Thank you, Valera ___ 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 oder Consulting für Ihr OTRS System? => http://www.otrs.de/
Re: [otrs] utf-8 and mysql
2005/8/29, bertagaz <[EMAIL PROTECTED]>: Erreur: Client does not support authentication protocol requested byserver; consider upgrading MySQL clientCommentaire: Please contact your adminRapport d'anomalie: [ Cliquer ici pour signaler une anomalie ! ] ... I'm kinda lost... Perl or mysql problem? Any idea? Thx by advanceBert.___OTRS mailing list: otrs - Webpage: http://otrs.org/Archive: http://lists.otrs.org/pipermail/otrsTo unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrsSupport oder Consulting für Ihr OTRS System?=> http://www.otrs.de/MySql Password Problem. The relevant info is Erreur: Client does not support authentication protocol requested by server; consider upgrading MySQL client MySql changed Password format between 4.0 and 4.1 The client library has to support the new format, or the passwords to access the Database have to be changed, in MySql, not OTRS . More info and workarounds from MySql side in http://dev.mysql.com/doc/mysql/en/old-client.html Sorry, but i don't know how it can be done from OTRS side. -- Hugo Hernán Buitrago RíosTecnólogo en Sistemas[EMAIL PROTECTED][EMAIL PROTECTED] ___ 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 oder Consulting für Ihr OTRS System? => http://www.otrs.de/
[otrs] utf-8 and mysql
Hi, I'm running otrs 1.3.2 on debian and trying to have full utf-8 support. With the basic install (mysql 4.0+apache2+otrs1.3.2), all works fine. My database was mysql 4.0, so I updated to 4.1 (server and clients) to have unicode enabled database. I set the default-character-set to utf8 in mysql, like mentionned in the FAQ, for both server and client, recreated the otrs database with utf-8 as default charset, converted a dump of the previous db to utf8 with iconv and reinjected it in mysql. The charset config of otrs is set to utf-8. But when I go to the main page I now have that error: --- Erreur: Client does not support authentication protocol requested by server; consider upgrading MySQL client Commentaire: Please contact your admin Rapport d'anomalie: [ Cliquer ici pour signaler une anomalie ! ] Trace du retour d'erreur: ERROR: OTRS-CGI-10 Perl: 5.8.4 OS: linux Time:Mon Aug 29 16:28:17 2005 Message: Client does not support authentication protocol requested by server; consider upgrading MySQL client Traceback(17547): Module: Kernel::System::DB::new (v1.40) Line: 222 Module: ModPerl::ROOT::ModPerl::Registry::var_www_otrs_index_2epl::handler (v) Line: 133 Module: (eval) (v1.73) Line: 203 Module: ModPerl::RegistryCooker::run (v1.73) Line: 203 Module: ModPerl::RegistryCooker::default_handler (v1.73) Line: 169 Module: ModPerl::Registry::handler (v1.99) Line: 30 I'm kinda lost... Perl or mysql problem? Any idea? Thx by advance Bert. ___ 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 oder Consulting für Ihr OTRS System? => http://www.otrs.de/
[otrs] UTF-8
Hi list, a lot of our customers receive Mail delivery errors from OTRS: [...] > Malformed UTF-8 character (unexpected non-continuation byte 0x72, immediately > after start byte 0xfc) in substitution (s///) at > /opt/otrs/Kernel/System/Ticket/Article.pm line 100. > Malformed UTF-8 character (unexpected non-continuation byte 0x72, immediately > after start byte 0xfc) in substitution (s///) at > /opt/otrs/Kernel/System/Ticket/Article.pm line 100. [...] Is there any way to tell OTRS to not send this kind of error reports ? The mails are delivered to OTRS. Thanks and regards Sascha ___ 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 oder Consulting für Ihr OTRS System? => http://www.otrs.de/
[otrs] utf-8 and 8bit problem
Hello, I've configured our otrs system to use UTF-8 charset. When otrs sends e-mail (agent or auto-reply), it uses 8bit as Content-Transfer-Encoding, like this: Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit I think this is correct, and my Evolution2 displays the message ok, however Mozilla (1.7), Lotus Notes and Outlook displays the raw unicode two bytes instead of the correct message. As I can't fix at least two out of them (in fact, 3 out of 3), is it possible to use quoted-printable as transfer-encoding instead of 8bit in otrs? Regards, Slapic ___ 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 oder Consulting für Ihr OTRS System? => http://www.otrs.de/
