User creation with encoding errors

I resolved this problem, it hasn’t anything to do with the request tracker and his dependent packages, also nothing with LDAP.
It was a debian problem in converting the input data to utf8.

Strange.

SamuelFrom: Jesse Vincent [mailto:jesse@bestpractical.com]
Sent: Friday,05 September,2003 22:23
To: Senoner Samuel

I don’t really want to update to a RC, also because I use debian apt to install my packages…
But if you can tell me wich patches to update to my 3.0.4…

Sorry, no.

One other thing I saw, is that when I change details or something else on the server with the problem, the characters are displayes correctly.
In this case, if I look into the database with my terminal, in the system with the problem I see ?? and in the other one, I see something like <0A>.
I can’t remember exactly because now I’am at home, and it’s 10 PM here.

RT stores everything in unicode, which is why they won’t display correctly on your iso-8859-1 terminal.

It is very strange because both systems should be identical.

Thanks for any ideas.

Samuel

-----Original Message-----
From: Jesse Vincent [mailto:jesse@bestpractical.com]
Sent: Fri 9/5/2003 9:52 PM
To: Senoner Samuel
Cc:
Subject: Re: [rt-users] User creation with encoding errors

I have two similar (almost identical) systems.

both Debian
both rt 3.0.4
both postgres 7.3.3
both searchbuilder 0.86

I have on both my LDAP User Lookup
This works on user creationn. If I have a User with an ä oder à somewhere, on one server I get following error:

Can you tell me if it’s still an issue with 3.0.5rc1?

[Fri Sep 5 17:04:21 2003] [warning]: DBD::Pg::st execute failed: ERROR: Invali
d UNICODE character sequence found (0xe4e000) at /usr/share/perl5/DBIx/SearchBui
lder/Handle.pm line 410.
(/usr/share/perl5/RT.pm:235)
[Fri Sep 5 17:04:21 2003] [warning]: RT::Handle=HASH(0x948cdc0) couldn’t execut
e the query ‘INSERT INTO Users (City, RealName, EmailAddress, Creator, Gecos, Pa
ssword, Country, LastUpdatedBy, Zip, WorkPhone, Created, id, Organization, Name,
LastUpdated) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)’ at /usr/shar
e/perl5/DBIx/SearchBuilder/Handle.pm line 417.
(/usr/share/perl5/RT.pm:235)
[Fri Sep 5 17:04:21 2003] [error]: Could not create a new user - (/usr/share/p
erl5/RT/User_Overlay.pm:277)
[Fri Sep 5 17:04:21 2003] [warning]: DBD::Pg::st execute failed: ERROR: curren
t transaction is aborted, queries ignored until end of transaction block at /usr
/share/perl5/DBIx/SearchBuilder/Handle.pm line 410.

Where can I find the difference in the encoding?
Or whould it be the best solution to convert my input by LDAP somewhere?
But I just import my data with LDAP and pass UserInfo to User Create.
But the strange thing is that the two servers are almost identic.

Do someone has an idea?

Jesse, I saw that somewhere a user wrote it also to the mailing list, you said to him to write directly to you.

I wanted to start using RT on Monday, but I suddently fount that everywhere in my Active Directory there are this strange characters, so I have this big problem.

Thank you

Samuel Senoner


Request Tracker — Best Practical Solutions – Trouble Ticketing. Free.

Request Tracker — Best Practical Solutions – Trouble Ticketing. Free.

Hi there,

I’m one of the maintainers of the Debian rt3 package.On Mon, Sep 08, 2003 at 05:51:32PM +0200, Senoner Samuel wrote:

I resolved this problem, it hasn’t anything to do with the request
tracker and his dependent packages, also nothing with LDAP. It was
a debian problem in converting the input data to utf8.

Can you be more specific about what caused this problem in Debian? It
would be great to be able to document it so that others do not have
the same trouble.

Thanks,

Stephen Quinney sjq@debian.org

I know. I thought about you later on.

I solved this problem making an apt-get upgrade.
At first I tried to update just request-tracker3. This didn’t solve
this.
Then I checked my libnet-ldap-perl, and they had the same version.

But in my opinion it has something to do with UTF and ISO conversion of
characters.

If you want, I can send you later directly more information.

SamuelFrom: Stephen Quinney
[mailto:stephen.quinney@computing-services.oxford.ac.uk]
Sent: Tuesday,09 September,2003 10:50
To: Senoner Samuel
Cc: rt-devel@lists.fsck.com

Hi there,

I’m one of the maintainers of the Debian rt3 package.

I have two similar (almost identical) systems.

both Debian
both rt 3.0.4
both postgres 7.3.3
both searchbuilder 0.86

I have on both my LDAP User Lookup
This works on user creationn. If I have a User with an ä oder à somewhere, on one server I get following error:

[Fri Sep 5 17:04:21 2003] [warning]: DBD::Pg::st execute failed: ERROR: Invali
d UNICODE character sequence found (0xe4e000) at /usr/share/perl5/DBIx/SearchBui
lder/Handle.pm line 410.
(/usr/share/perl5/RT.pm:235)
[Fri Sep 5 17:04:21 2003] [warning]: RT::Handle=HASH(0x948cdc0) couldn’t execut
e the query ‘INSERT INTO Users (City, RealName, EmailAddress, Creator, Gecos, Pa
ssword, Country, LastUpdatedBy, Zip, WorkPhone, Created, id, Organization, Name,
LastUpdated) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)’ at /usr/shar
e/perl5/DBIx/SearchBuilder/Handle.pm line 417.
(/usr/share/perl5/RT.pm:235)
[Fri Sep 5 17:04:21 2003] [error]: Could not create a new user - (/usr/share/p
erl5/RT/User_Overlay.pm:277)
[Fri Sep 5 17:04:21 2003] [warning]: DBD::Pg::st execute failed: ERROR: curren
t transaction is aborted, queries ignored until end of transaction block at /usr
/share/perl5/DBIx/SearchBuilder/Handle.pm line 410.

Where can I find the difference in the encoding?
Or whould it be the best solution to convert my input by LDAP somewhere?
But I just import my data with LDAP and pass UserInfo to User Create.
But the strange thing is that the two servers are almost identic.

Do someone has an idea?

Jesse, I saw that somewhere a user wrote it also to the mailing list, you said to him to write directly to you.

I wanted to start using RT on Monday, but I suddently fount that everywhere in my Active Directory there are this strange characters, so I have this big problem.

Thank you

Samuel Senoner