Dumpfile-to-rt-3.0 fails with errors

RT Users
1

Hello,

I’m trying to update rt-2 to rt-3 on the same box running redhat 7.3,
perl 5.6.1, apache 1.3.27

When running dumpfile-to-rt-3.0 to import the database, I get the
following error:

…
.t-816
.t-817
.t-818
Can’t locate object method “warn” via package “Log::Dispatch” (perhaps
you forgot to load “Log::Dispatch”?) at
/opt/rt3/lib/RT/CachedGroupMember_Overlay.pm line 91.

I’ve checked that Log::Dispatch is installed and have added the line:

use Log::Dispatch;

to dumpfile-to-rt-3.0 to no avail.

Does anyone have any idea what’s going on here? I’m not opposed to
removing the offending tickets as the data is old and not that
important, but I don’t want to do it if I wind up deleting a large
number of tickets.

Any help would be appreciated.

Regards,
Joseph

2

Forgot to mention that I’m using version 1.9 of the dumpfile-to-rt-3.0
tool.

j-On Thu, 2003-10-09 at 15:50, Joseph M Bironas wrote:

Hello,

I’m trying to update rt-2 to rt-3 on the same box running redhat 7.3,
perl 5.6.1, apache 1.3.27

When running dumpfile-to-rt-3.0 to import the database, I get the
following error:

…
.t-816
.t-817
.t-818
Can’t locate object method “warn” via package “Log::Dispatch” (perhaps
you forgot to load “Log::Dispatch”?) at
/opt/rt3/lib/RT/CachedGroupMember_Overlay.pm line 91.

I’ve checked that Log::Dispatch is installed and have added the line:

use Log::Dispatch;

to dumpfile-to-rt-3.0 to no avail.

Does anyone have any idea what’s going on here? I’m not opposed to
removing the offending tickets as the data is old and not that
important, but I don’t want to do it if I wind up deleting a large
number of tickets.

Any help would be appreciated.

Regards,
Joseph

3

Joseph M Bironas wrote:

Forgot to mention that I’m using version 1.9 of the dumpfile-to-rt-3.0
tool.

That’s ancient. 1.20 is current.

I’m trying to update rt-2 to rt-3 on the same box running redhat 7.3,
perl 5.6.1, apache 1.3.27

Also note that perl 5.6.1 is really not recommended for RT3.

Phil Homewood, Systems Janitor, http://www.SnapGear.com
pdh@snapgear.com Ph: +61 7 3435 2810 Fx: +61 7 3891 3630
SnapGear - Custom Embedded Solutions and Security Appliances

4

Okay, updated to the latest 1.20. Thanks for that one, pure oversight on
my part.

Now I’m running into a different problem, here’s the output:

.t-650
.t-651
.t-652
.t-655
[Fri Oct 10 02:21:32 2003] [error]: Couldn’t create a ticket group of
type ‘AdminCc’ for ticket 655: Could not create group
(/opt/rt3/lib/RT/Ticket_Overlay.pm:1323)
[Fri Oct 10 02:21:32 2003] [crit]: Couldn’t create ticket groups for
ticket 655. aborting Ticket creation.
(/opt/rt3/lib/RT/Ticket_Overlay.pm:534)
.t-656
[Fri Oct 10 02:21:32 2003] [crit]: Couldn’t create a ticket
(/opt/rt3/lib/RT/Ticket_Overlay.pm:518)

The script continues through the process throwing “[crit]: Couldn’t
create a ticket” errors on the remaining tickets. It does not import
anything past the point of the initial error.

Any ideas of how to remedy this?

Regards,
JosephOn Thu, 2003-10-09 at 16:12, Phil Homewood wrote:

Joseph M Bironas wrote:

Forgot to mention that I’m using version 1.9 of the dumpfile-to-rt-3.0
tool.

That’s ancient. 1.20 is current.

I’m trying to update rt-2 to rt-3 on the same box running redhat 7.3,
perl 5.6.1, apache 1.3.27

Also note that perl 5.6.1 is really not recommended for RT3.

5

Joseph M Bironas wrote:

[Fri Oct 10 02:21:32 2003] [error]: Couldn’t create a ticket group of
type ‘AdminCc’ for ticket 655: Could not create group
(/opt/rt3/lib/RT/Ticket_Overlay.pm:1323)

Are you starting with a clean rt3 database? Have you re-exported
the rt2 data using the latest 2.0-to-dumpfile? The dumpfile created
by your old scripts might be a little bogus…
Phil Homewood, Systems Janitor, http://www.SnapGear.com
pdh@snapgear.com Ph: +61 7 3435 2810 Fx: +61 7 3891 3630
SnapGear - Custom Embedded Solutions and Security Appliances

6

Are you starting with a clean rt3 database? Have you re-exported
the rt2 data using the latest 2.0-to-dumpfile? The dumpfile created
by your old scripts might be a little bogus…

Yes, starting with a fresh RT3 db. Re-exported with the latest
rt-2.0-to-dumpfile. Removed the old dump directory before exporting too.

Did some searching in the original RT2 tickets and in the dump file for
the specific ticket itself, I can’t find any reference to an AdminCC for
the failing ticket at all.

j-