Hi.
 
I got them recently with OTRS 2.1.x set up to run UTF-8. Changing the charset to ISO-8859-1 fixed it. Upgrading to a newser version also fixed it, still allowing me to run UTF-8.
 
 
--
Lars

From: otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] On Behalf Of Mike Dent
Sent: Thursday, May 22, 2008 7:27 PM
To: User questions and discussions about OTRS.org
Subject: [otrs] Recently getting these errors fro OTRS :- Malformed UTF-8 character (unexpected ......

Hi,
3 days ago i noticed i started getting messages from cron daemon on my OTRS box of the form:-


Malformed UTF-8 character (unexpected continuation byte 0xa9, with no preceding start byte) in substitution iterator at /opt/otrs/Kernel/System/EmailParser.pm line 655, <PRODUCT> line 4.
Malformed UTF-8 character (unexpected continuation byte 0xa9, with no preceding start byte) in substitution iterator at /opt/otrs/Kernel/System/EmailParser.pm line 655, <PRODUCT> line 4.
Malformed UTF-8 character (unexpected continuation byte 0xa9, with no preceding start byte) in substitution (s///) at /opt/otrs/Kernel/System/EmailParser.pm line 669, <PRODUCT> line 4.
Malformed UTF-8 character (unexpected continuation byte 0xa9, with no preceding start byte) in substitution (s///) at /opt/otrs/Kernel/System/EmailParser.pm line 670, <PRODUCT> line 4.
Malformed UTF-8 character (unexpected continuation byte 0xa9, with no preceding start byte) in substitution (s///) at /opt/otrs/Kernel/System/EmailParser.pm line 671, <PRODUCT> line 4.
Malformed UTF-8 character (unexpected continuation byte 0xa9, with no preceding start byte) in substitution (s///) at /opt/otrs/Kernel/System/EmailParser.pm line 672, <PRODUCT> line 4.
Malformed UTF-8 character (unexpected continuation byte 0xa9, with no preceding start byte) in substitution (s///) at /opt/otrs/Kernel/System/EmailParser.pm line 674, <PRODUCT> line 4.
Malformed UTF-8 character (unexpected continuation byte 0xa9, with no preceding start byte) in substitution (s///) at /opt/otrs/Kernel/System/EmailParser.pm line 675, 

etc etc

Since this time I am receiving no notifications from OTRS and no tickets are being created.

I checked /var/log/messages and noticed at the time I started getting these reports from cron, the log was showing:-

May 19 19:30:05 rt3 OTRS-PM3-30[14784]: [Notice][Kernel::System::PID::PIDCreate] Can't create PID PostMasterPOP3, because it's already running (rt3.blah.local/14612)
! 

And every so often I get:-

May 20 10:30:04 rt3 OTRS-PM3-30[30434]: [Notice][Kernel::System::PID::PIDCreate] Removed PID (PostMasterPOP3/rt3.blah.local/29415, because 1 hour old! 
May 20 10:40:05 rt3 OTRS-PM3-30[30620]: [Notice][Kernel::System::PID::PIDCreate] Can't create PID PostMasterPOP3, because it's already running (rt3.blah.local/30434)

I'm running otrs 2.1.7

Any pointers as what might have gone wrong?

Thanks
Mike