Rt2 -> rt3 version 1.12 failure

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I am still running into errors while attempting to upgrade to rt3.0.1.

I have discovered that if I remove the tickets after they have been
imported using dumpfile-to-rt-3.0, the script will move on to next
ticket that failed to be imported on the first run. This ticket will be
imported along with a handful of others, and then the error about the
"NewValue for HASH" comes up again. If I remove the next batch of
tickets which happened to be imported, and then start the script again
it will continue to import another random size group of tickets, and
once again end in the HASH error below.

I did this for a while. It seems that this method is imperfect and will
probably not work.

I am running mysql 4.0.12, perl-5.8.0, and have all of the modules
needed to run rt3.
I have tried this script under Linux, Solaris, and FreeBSD, all end with
the same error. I think it has something to do with the way the rt data
is laid out for the old version?

Cheers,

  • -b. ash

Importing groups
[Tue May 13 22:35:34 2003] [crit]: 1
(/usr/local/rt3/lib/RT/ACE_Overlay.pm:884)
[Tue May 13 22:35:34 2003] [crit]: Can’t load a principal for id
(/usr/local/rt3/lib/RT/ACE_Overlay.pm:885)
Importing tickets…t-1
.t-2
.t-3
.t-4
.t-5
.t-6
.t-7
.t-8
.t-9
.t-10
.t-11
.t-12
t-4
t-5
t-6
t-7
t-8
t-9
t-10
t-11
t-12
t-13
t-14
t-15
t-16
t-17
t-18
t-19
t-20
t-21
t-22
t-23
t-24
t-25
t-26
t-27
t-28
t-29
t-30
t-31
t-32

[Tue May 13 22:39:54 2003] [crit]: What do I do with NewValue for
HASH(0x90eec48). It is a HASH at dumpfile-to-rt-3.0 line 347.
~ (/usr/local/rt3/lib/RT.pm:228)


  • ------------------ <-=-> ----------------------
    Benjamin Ash
    Systems Analyst II
    ECE Dept. University of New Mexico | University of New Mexico, 87131
    +1 505 277 1082 /Fax +1 505 277 1439 | e-mail: bash@eece.unm.edu
  • ------------------ <-o-> ----------------------
    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.2.1 (GNU/Linux)
    Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE+wXahXkk94+rPTdoRAihzAKC/QNfC77v2gWBwe/uhrPX3EdiBOQCdFv+8
61exvJxaAaomNws4VYO1Mi4=
=b02c
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I am still running into errors while attempting to upgrade to rt3.0.1.

I have discovered that if I remove the tickets after they have been
imported using dumpfile-to-rt-3.0, the script will move on to next
ticket that failed to be imported on the first run. This ticket will be
imported along with a handful of others, and then the error about the
"NewValue for HASH" comes up again.

Can you send us the ticket dump file that contains the hash for
NewValue?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I am still running into errors while attempting to upgrade to rt3.0.1.

I have discovered that if I remove the tickets after they have been
imported using dumpfile-to-rt-3.0, the script will move on to next
ticket that failed to be imported on the first run. This ticket will be
imported along with a handful of others, and then the error about the
"NewValue for HASH" comes up again.

Can you send us the ticket dump file that contains the hash for
NewValue?

I’ve been experiencing the same problems since around the 1.9 import util.

My dump->rt3 gets to ticket2 then craps out on the same error, though
different HASH reference.

Attached is my ticket #2.

If it means anything, this was a ticket that has since been imported from
the 1.x series to 2.x. Also, I have pruned old killed tickets in the past,
and there is NOT a t-3 listed. Could this be the culprit?

Running FreeBSD, perl5.6.1, mysql4.0.12.

–c

Cassidy B. Larson – Network Operations Manager
InfoWest, Inc. * 596 E. Tabernacle * St. George, UT 84770
Voice: 435-674-0165 * FAX: 435-674-9654
butch@infowest.com

t-2 (7.97 KB)

Hi,

I have attached t-32 and t-33, t-32 seems to get imported correctly, it
seems to be t-33 that causes the problems with the hash for NewValue.

b. ash

Jesse Vincent wrote:>On Tue, May 13, 2003 at 04:50:09PM -0600, B. Ash wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I am still running into errors while attempting to upgrade to rt3.0.1.

I have discovered that if I remove the tickets after they have been
imported using dumpfile-to-rt-3.0, the script will move on to next
ticket that failed to be imported on the first run. This ticket will be
imported along with a handful of others, and then the error about the
"NewValue for HASH" comes up again.

Can you send us the ticket dump file that contains the hash for
NewValue?

------------------ <-=-> ----------------------
Benjamin Ash
Systems Analyst II
ECE Dept. University of New Mexico | University of New Mexico, 87131
+1 505 277 1082 /Fax +1 505 277 1439 | e-mail: bash@eece.unm.edu

t-32 (9.99 KB)

t-33 (19.6 KB)

Not sure if Jesse has had a chance to look at this issue yet or not.

I found out, that ticket #2 did get imported correctly, though ticket #4 did
not. Attached is the dump of t-4. Does anyone think that as there is no t-3
(from pruning killed tickets), that it might be the reason to crap out?

–cassidy

I’ve been experiencing the same problems since around the 1.9 import util.

My dump->rt3 gets to ticket2 then craps out on the same error, though
different HASH reference.

Attached is my ticket #2.

If it means anything, this was a ticket that has since been imported from
the 1.x series to 2.x. Also, I have pruned old killed tickets in the past,
and there is NOT a t-3 listed. Could this be the culprit?

Running FreeBSD, perl5.6.1, mysql4.0.12.

Cassidy B. Larson – Network Operations Manager
InfoWest, Inc. * 596 E. Tabernacle * St. George, UT 84770
Voice: 435-674-0165 * FAX: 435-674-9654
butch@infowest.com

t-4.bin (11.5 KB)