Dumpfile-to-rt-3.0 failed (2.0.14 - 3.8.8)

Dear list members,

we would like to convert our 9 year old rt2 (2.0.14 from 02/2002)
to the current rt3 3.8.8.

Therefore,

  • I downloaded your migration tool from
    https://github.com/bestpractical/rt2-to-rt3 and
  • created a dump directory using rt-2.0-to-dumpfile and
  • tried to import the dump using dumpfile-to-rt-3.0 to the new RT3
    mysql-db but
    I get the following errors …

[Fri Feb 11 23:14:14 2011] [warning]: Use of uninitialized value in
string eq at /usr/bin/dumpfile-to-rt-3.0 line 891.
(/usr/bin/dumpfile-to-rt-3.0:891)
[Fri Feb 11 23:14:14 2011] [warning]: Use of uninitialized value in
length at /opt/rt3/lib/RT/Record.pm line 753.
(/opt/rt3/lib/RT/Record.pm:753)
[Fri Feb 11 23:14:14 2011] [warning]: Use of uninitialized value in
string eq at /usr/bin/dumpfile-to-rt-3.0 line 970.
(/usr/bin/dumpfile-to-rt-3.0:970)
aattta[Fri Feb 11 23:14:14 2011] [warning]: Use of uninitialized value
in string eq at /usr/bin/dumpfile-to-rt-3.0 line 891.
(/usr/bin/dumpfile-to-rt-3.0:891)
[Fri Feb 11 23:14:14 2011] [warning]: Use of uninitialized value in
length at /opt/rt3/lib/RT/Record.pm line 753.
(/opt/rt3/lib/RT/Record.pm:753)

Importing links
l[Fri Feb 11 23:14:27 2011] [warning]: Use of uninitialized value in
concatenation (.) or string at /usr/bin/dumpfile-to-rt-3.0 line 434.
(/usr/bin/dumpfile-to-rt-3.
0:434)
[Fri Feb 11 23:14:27 2011] [warning]: Use of uninitialized value in
concatenation (.) or string at /usr/bin/dumpfile-to-rt-3.0 line 440.
(/usr/bin/dumpfile-to-rt-3.0
:440)


Could not create scrip: On Correspond Notify Requestors And Ccs with
template Correspondence_ DT N_deutsch in queue #5

  • may be due to a non-standard template, condition or action

Could not create scrip: On Comment Notify Owner As Comment with template
Admin Comment_ DT N_deutsch in queue #5

  • may be due to a non-standard template, condition or action

So, only the tickets NOT assigned to any queue where merged. All ticked
assigned to
a queue are missing.

Could somebody help me to track down this slight migration problem ?

Kind regards
Danny

  • I downloaded your migration tool from
    https://github.com/bestpractical/rt2-to-rt3 and
  • created a dump directory using rt-2.0-to-dumpfile and
  • tried to import the dump using dumpfile-to-rt-3.0 to the new RT3
    mysql-db but
    I get the following errors …

So, only the tickets NOT assigned to any queue where merged. All
ticked
assigned to a queue are missing.

Small correction - it seems that all the tickets are imported
Are the errors/warning a problem ? May the import was not done 100% ?

Kind regards
Danny

  • I downloaded your migration tool from
    https://github.com/bestpractical/rt2-to-rt3 and
  • created a dump directory using rt-2.0-to-dumpfile and
  • tried to import the dump using dumpfile-to-rt-3.0 to the new RT3
    mysql-db but
    I get the following errors …

So, only the tickets NOT assigned to any queue where merged. All
ticked
assigned to a queue are missing.

Small correction - it seems that all the tickets are imported
Are the errors/warning a problem ? May the import was not done 100% ?

This reads like you had trouble rewriting your Links, often this is
because your Organization is invalid or because you changed it from
rt2 to rt3.

The Scrip part is likely because you had custom templates that won’t
work on rt3 since the APIs changed and you’ll need to recreate them.

-kevin

Hi,

a) I started the import now by erasing the predefined database:

/opt/rt3/sbin/rt-setup-database --action drop --dba root

–dba-password xx
/opt/rt3/sbin/rt-setup-database --action create --dba root
–dba-password xx
/opt/rt3/sbin/rt-setup-database --action schema --dba root
–dba-password xx
/opt/rt3/sbin/rt-setup-database --action acl --dba root
–dba-password xx
/opt/rt3/sbin/rt-setup-database --action coredata --dba root
–dba-password xx

This helps me to track down other issues e.g. the imported tickets has
no assigned owner.
May this could be a small note in your dumpfile-to-rt-3.0-README .

b) Links

This reads like you had trouble rewriting your Links, often this is
because your Organization is invalid or because you changed it from
rt2 to rt3.

OK - this is correct - we changed the name back to the old version,
but warnings concerning the ticket import are still available.
Any additional hints ?

Importing links
l[Tue Feb 15 20:12:28 2011] [warning]: Use of uninitialized value in
concatenation (.) or string at /usr/bin/dumpfile-to-rt-3.0 line 434.
(/usr/bin/dumpfile-to-rt-3.0:434)
[Tue Feb 15 20:12:28 2011] [warning]: Use of uninitialized value in
concatenation (.) or string at /usr/bin/dumpfile-to-rt-3.0 line 440.
(/usr/bin/dumpfile-to-rt-3.0:440)

Skipping link creation (21 4 MemberOf) because duplicate of 2 detected
Skipping link creation (30 30 MergedInto) because duplicate of 9
detected

What are exactly the “Links” ? So, may they are not important for the
migration ?

c) Import of tickets
Concerning the normal ticket import, I got this kind of warning for each
ticket:

t-35437: [Tue Feb 15 20:09:42 2011] [warning]: Use of uninitialized
value in hash element at /usr/bin/dumpfile-to-rt-3.0 line 667.
(/usr/bin/dumpfile-to-rt-3.0:667)
line 667: $ticket->{‘Owner’} = $user_map->{
$ticket->{‘Owner’} };

wta[Tue Feb 15 20:09:42 2011] [warning]: Use of uninitialized value in
string eq at /usr/bin/dumpfile-to-rt-3.0 line 891.
(/usr/bin/dumpfile-to-rt-3.0:891)
line: 891: if ( $content_type =~
qr{(text/|message/rfc822)}i )

[Tue Feb 15 20:09:42 2011] [warning]: Use of uninitialized value in
length at /opt/rt3/lib/RT/Record.pm line 753.
(/opt/rt3/lib/RT/Record.pm:753)
line: 753 #if the attachment is larger than the
maximum size

		        if ( ($MaxSize) and ( $MaxSize <

length($Body) ) ) {

[Tue Feb 15 20:09:42 2011] [warning]: Use of uninitialized value in
string eq at /usr/bin/dumpfile-to-rt-3.0 line 970.
(/usr/bin/dumpfile-to-rt-3.0:970)
aat
line 970: if ($a->{ContentEncoding} eq
’base64’

c) Scrips

The Scrip part is likely because you had custom templates that won’t
work on rt3 since the APIs changed and you’ll need to recreate them.

Ok - np.

Kind regards
Danny

Hi,

a) I started the import now by erasing the predefined database:

This helps me to track down other issues e.g. the imported tickets has
no assigned owner.
May this could be a small note in your dumpfile-to-rt-3.0-README .

The upgrader assumes a clean DB (since it is a conversion tool).
If you want to merge into an existing 3.x system, check the MERGING
section. Patches against the git repo to improve the documentation
are appreciated.

Importing links
l[Tue Feb 15 20:12:28 2011] [warning]: Use of uninitialized value in
concatenation (.) or string at /usr/bin/dumpfile-to-rt-3.0 line 434.
(/usr/bin/dumpfile-to-rt-3.0:434)
[Tue Feb 15 20:12:28 2011] [warning]: Use of uninitialized value in
concatenation (.) or string at /usr/bin/dumpfile-to-rt-3.0 line 440.
(/usr/bin/dumpfile-to-rt-3.0:440)

Skipping link creation (21 4 MemberOf) because duplicate of 2 detected
Skipping link creation (30 30 MergedInto) because duplicate of 9
detected

What are exactly the “Links” ? So, may they are not important for the
migration ?

Links are merges, parent/child, etc
They’re important if you use those features
This still implies that you have incorrect link structures in your rt2
database since the cache isn’t being populated.

c) Import of tickets
Concerning the normal ticket import, I got this kind of warning for each
ticket:

t-35437: [Tue Feb 15 20:09:42 2011] [warning]: Use of uninitialized
value in hash element at /usr/bin/dumpfile-to-rt-3.0 line 667.
(/usr/bin/dumpfile-to-rt-3.0:667)
line 667: $ticket->{‘Owner’} = $user_map->{
$ticket->{‘Owner’} };

wta[Tue Feb 15 20:09:42 2011] [warning]: Use of uninitialized value in
string eq at /usr/bin/dumpfile-to-rt-3.0 line 891.
(/usr/bin/dumpfile-to-rt-3.0:891)
line: 891: if ( $content_type =~
qr{(text/|message/rfc822)}i )

[Tue Feb 15 20:09:42 2011] [warning]: Use of uninitialized value in
length at /opt/rt3/lib/RT/Record.pm line 753.
(/opt/rt3/lib/RT/Record.pm:753)
line: 753 #if the attachment is larger than the
maximum size

  	        if ( ($MaxSize) and ( $MaxSize <

length($Body) ) ) {

[Tue Feb 15 20:09:42 2011] [warning]: Use of uninitialized value in
string eq at /usr/bin/dumpfile-to-rt-3.0 line 970.
(/usr/bin/dumpfile-to-rt-3.0:970)
aat
line 970: if ($a->{ContentEncoding} eq
’base64’

You may wish to try the current git version and see if any of the
unreleased patches help.

-kevin