Import sadness

Hi all,

Well, after putting in a proper Apache with mod_perl, and installing
postgres from source, I have a working RT2. However, the import
mysteriously fails after only a few hundred tickets.

The last lines are depressingly uninformative:

611.merging into 611…transactions: 3638.3639.3640.3641.done.

612…transactions: 3642.3643.3644.3645.3646.3647.3648.done.

613…transactions: 3649.3650.3651.3652.done.

614…transactions: 3653.3654.3655.3656.done.

615…transactions:

At this point, looking in apache’s logs for the RT1 installation, it’s
apparent that mysql dumped core (I am importing from another machine,
but the transaction files are nfs-mounted, so they should come over
fine–if I ever get that far). The MySQL version is 3.22.32.

I contemplate simply dumping the db and loading it into a mysql
instance on the same host as where RT2 is, but I’m not sure if this
will really help.

Any suggestions on troubleshooting this vexing problem? We have about
28,000 tickets, and it would obviously be way nifty if we could get
them imported over smoothly.

–JB

At this point, looking in apache’s logs for the RT1 installation, it’s
apparent that mysql dumped core (I am importing from another machine,
but the transaction files are nfs-mounted, so they should come over
fine–if I ever get that far). The MySQL version is 3.22.32.

There should actually be an rt logfile in /tmp…

I contemplate simply dumping the db and loading it into a mysql
instance on the same host as where RT2 is, but I’m not sure if this
will really help.

That actually should help a lot. Give that a shot.

-j

Any suggestions on troubleshooting this vexing problem? We have about
28,000 tickets, and it would obviously be way nifty if we could get
them imported over smoothly.

–JB


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

http://www.bestpractical.com/products/rt – Trouble Ticketing. Free.