Problems with rt2-to-rt3 v1.20

RT Developers
1

Hi there,

I am having trouble with the rt2 to rt3 conversion scripts. The
rt2-to-dumpfile scripts seems to work fine and I have what looks like
a correct dumpfile. When I run dumpfile-to-rt3, it says:

“Importing users
u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.”

but looking at the database logs while it is doing this shows nothing
is actually succeeding:

ERROR: pg_atoi: error in " “fake address” fake@example.org":
can’t parse " “fake address” fake@example.org"

(I get something like that for every attempt to import a user).

The dumpfile was created with v1.20, both the rt2 and rt3 databases
are PostgreSQL 7.2.1, RT is 3.0.3.

Any suggestions?

Thanks,

Stephen Quinney

2

Hi there,

I am having trouble with the rt2 to rt3 conversion scripts. The
rt2-to-dumpfile scripts seems to work fine and I have what looks like
a correct dumpfile. When I run dumpfile-to-rt3, it says:

ERROR: pg_atoi: error in " “fake address” fake@example.org":
can’t parse " “fake address” fake@example.org"

OK, to followup to my own post it seems that it does manage to
actually insert all the users into the database even though it
complains bitterly for every entry. It totally fails though on the
group import stage:

Importing groups
gNOTICE: current transaction is aborted, queries ignored until end of transaction block
[Wed Aug 13 11:36:32 2003] [crit]: No such pseudo-hash field “HASH(0xb665ee8)” at /home/stephen/rt2-to-rt3-v1.20/dumpfile-to-rt-3.0 line 133.
(/usr/share/perl5/RT.pm:242)

No idea, what is causing this, I’ll poke around some more and try to
come up with some ideas.

Stephen

3

OK, to followup to my own post it seems that it does manage to
actually insert all the users into the database even though it
complains bitterly for every entry. It totally fails though on the
group import stage:

Importing groups
gNOTICE: current transaction is aborted, queries ignored until end of transaction block
[Wed Aug 13 11:36:32 2003] [crit]: No such pseudo-hash field “HASH(0xb665ee8)” at /home/stephen/rt2-to-rt3-v1.20/dumpfile-to-rt-3.0 line 133.
(/usr/share/perl5/RT.pm:242)

No idea, what is causing this, I’ll poke around some more and try to
come up with some ideas.

I had a similar problem, turns out it was my own silliness in emptying
out the database manually and not running the sbin/rt-setup-database
script to get it back to it’s freshly installed state. See my mail of
July 29th for the exact error - slightly different line number, but it
was an older version of the migration tools.

Daniel Foster
Technical Director

4

Hi there,

I am having trouble with the rt2 to rt3 conversion scripts. The
rt2-to-dumpfile scripts seems to work fine and I have what looks like
a correct dumpfile. When I run dumpfile-to-rt3, it says:

“Importing users
u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.u.”

but looking at the database logs while it is doing this shows nothing
is actually succeeding:

ERROR: pg_atoi: error in " “fake address” fake@example.org":
can’t parse " “fake address” fake@example.org"

Ok, after investigation it seems this error is ignorable. The problem
is that the subroutine load_user() first tries to load the user with
the user_id considered as the email address, then considered as the
name and then finally the id (which is an integer). A change of the
if{} statement in load_user() to only try the id field when the user_id
is numeric gets rid of the annoying error messages.

Stephen

The patch for the small change I made is:

— dumpfile-to-rt-3.0.orig Wed Aug 13 14:56:24 2003
+++ dumpfile-to-rt-3.0 Wed Aug 13 14:55:45 2003
@@ -448,13 +448,13 @@
}
else {
$user_objects{$user_id} = RT::User->new($RT::SystemUser);

  •    if ( $user_id =~ /@/ ) {

  •    if ( $user_id =~ /^\d+$/ ) {

  •        $user_objects{$user_id}->LoadByCols( id => $user_id );

  •    }

  •   elsif ( $user_id =~ /@/ ) {
       $user_objects{$user_id}->LoadByCols( EmailAddress => $user_id );
       unless ( $user_objects{$user_id}->id ) {
           $user_objects{$user_id}->LoadByCols( Name => $user_id );

  •        }

  •        unless ( $user_objects{$user_id}->id ) {

  •            $user_objects{$user_id}->LoadByCols( id => $user_id );
       }
   }
   else {
5

ERROR: pg_atoi: error in " “fake address” fake@example.org":
can’t parse " “fake address” fake@example.org"

(I get something like that for every attempt to import a user).

The dumpfile was created with v1.20, both the rt2 and rt3 databases
are PostgreSQL 7.2.1, RT is 3.0.3.

Can you verify that you have the same problem with Postgres 7.3 and RT
3.0.4 (or even 3.0.5pre2) if you can.

Thanks,
Jesse

Any suggestions?

Thanks,

Stephen Quinney

rt-devel mailing list
rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel

Request Tracker... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.

6

And then I saw your later message. I’ll get that patch into place for
1.21.

JesseOn Wed, Aug 13, 2003 at 04:28:14PM -0400, Jesse Vincent wrote:

ERROR: pg_atoi: error in " “fake address” fake@example.org":
can’t parse " “fake address” fake@example.org"

(I get something like that for every attempt to import a user).

The dumpfile was created with v1.20, both the rt2 and rt3 databases
are PostgreSQL 7.2.1, RT is 3.0.3.

Can you verify that you have the same problem with Postgres 7.3 and RT
3.0.4 (or even 3.0.5pre2) if you can.

Thanks,
Jesse

Any suggestions?

Thanks,

Stephen Quinney

rt-devel mailing list
rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel

–
Request Tracker... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.

Request Tracker... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.