[rt-users] rt2 -> rt3 version 1.12 failure.
Cassidy B. Larson
butch at infowest.com
Wed May 14 01:46:22 EDT 2003
On 5/13/03 7:35 PM, "Jesse Vincent" <jesse at bestpractical.com> 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?
>
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 at infowest.com
----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: t-2
Type: application/octet-stream
Size: 8162 bytes
Desc: not available
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20030513/bc1492d2/attachment.obj>
More information about the rt-users
mailing list