Best practices to follow when migrating RT2 to RT3 and mysql errors

Dear List,

On a fresh RT-3.0.9 I have attempted to migrate our fairly substantial
RT-2.0.15 database. mysql-4.0.17 on both ends.

When running dumpfile-to-rt-3.0 the script barfs out an mysql error,
referring to max_allowed_packet .

The attachment in question (see below) is 1155441 bytes large, the
workstation I’m running this on is 256 MB RAM, and I increased
max_allowed_packet in my.cnf from (no value) to 256 MB. I also
tried it at 128 MB. Still same error.

What would best practices be at this point to get the database migrated?

I reported this to the dev list, and basically was as we used to say,
“shone off.” Which is fine, but somebody must have run into this before.

Thanks for any assistance or further suggestions for reading material.

Meant to send the error, not the full attachment. Here it is:

.t-395
Couldn’t create attachment
$VAR1 = {
‘Subject’ => ‘’,
‘ContentType’ => ‘text/plain’,
‘Filename’ => ‘media-inc.log’,
‘Headers’ => 'Content-Type: TEXT/PLAIN; charset=US-ASCII;
name=“media-inc.log”
Content-Transfer-Encoding: BASE64
Content-ID: Pine.LNX.4.44.0306031556040.16591@web0.speakeasy.net
Content-Description:
Content-Disposition: attachment; filename=“media-inc.log”
X-RT-Original-Encoding: us-ascii
',
‘Creator’ => ‘4’,
‘Parent’ => ‘1501’,
‘Created’ => ‘2003-06-03 22:45:31’,
‘ContentEncoding’ => ‘none’,
‘id’ => ‘1503’,
‘TransactionId’ => ‘2238’
};

Got a packet bigger than ‘max_allowed_packet’
[Thu Feb 19 01:35:58 2004] [crit]: Died at ./dumpfile-to-rt-3.0 line 714.
(/opt/rt3/lib/RT.pm:254)

Dear List,

On a fresh RT-3.0.9 I have attempted to migrate our fairly substantial
RT-2.0.15 database. mysql-4.0.17 on both ends.

When running dumpfile-to-rt-3.0 the script barfs out an mysql error,
referring to max_allowed_packet .

The attachment in question (see below) is 1155441 bytes large, the
workstation I’m running this on is 256 MB RAM, and I increased
max_allowed_packet in my.cnf from (no value) to 256 MB. I also
tried it at 128 MB. Still same error.

What would best practices be at this point to get the database migrated?

I reported this to the dev list, and basically was as we used to say,
“shone off.” Which is fine, but somebody must have run into this before.

Thanks for any assistance or further suggestions for reading material.

±------------------------


rt-users mailing list
rt-users@lists.bestpractical.com
The rt-users Archives

Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm

Dear List,

On a fresh RT-3.0.9 I have attempted to migrate our fairly substantial
RT-2.0.15 database. mysql-4.0.17 on both ends.

When running dumpfile-to-rt-3.0 the script barfs out an mysql error,
referring to max_allowed_packet .

I reported this to the dev list, and basically was as we used to say,
“shone off.” Which is fine, but somebody must have run into this before.

Well, I told you to look at mysql’s documentation and then pointed you
at the specific reference for how to fix it. I’m not quite sure how that
counts as “shone off.” But the documentation does tell you how to
configure mysql to do the right thing. It was:

http://www.mysql.com/doc/en/Packet_too_large.html

Thanks for any assistance or further suggestions for reading material.

±------------------------


rt-users mailing list
rt-users@lists.bestpractical.com
The rt-users Archives

Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm

Request Tracker — Best Practical Solutions – Trouble Ticketing. Free.

Well, I told you to look at mysql’s documentation and then pointed you
at the specific reference for how to fix it. I’m not quite sure how that
counts as “shone off.” But the documentation does tell you how to
configure mysql to do the right thing. It was:

http://www.mysql.com/doc/en/Packet_too_large.html
I had to bump this up twice during a recent upgrade, and it was
surprising how big those darn attachments really get. :wink:

Nate Duehr nate@natetech.com

I did that, same error. As previously attempted to explain.

(I raised the max_allowed_packet even tho the mysql doc implies it
is not needed in 4.X, and upon doing so saw no gain in RT migration)

So if anyone wants to suggest something else it would probably be helpful.

Thanks.

On Wed, Feb 18, 2004 at 06:15:06PM -0800, David M Dennis wrote:

Dear List,

On a fresh RT-3.0.9 I have attempted to migrate our fairly substantial
RT-2.0.15 database. mysql-4.0.17 on both ends.

When running dumpfile-to-rt-3.0 the script barfs out an mysql error,
referring to max_allowed_packet .

I reported this to the dev list, and basically was as we used to say,
“shone off.” Which is fine, but somebody must have run into this before.

Well, I told you to look at mysql’s documentation and then pointed you
at the specific reference for how to fix it. I’m not quite sure how that
counts as “shone off.” But the documentation does tell you how to
configure mysql to do the right thing. It was:

http://www.mysql.com/doc/en/Packet_too_large.html

Thanks for any assistance or further suggestions for reading material.

±------------------------


rt-users mailing list
rt-users@lists.bestpractical.com
The rt-users Archives

Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm


Request Tracker — Best Practical Solutions – Trouble Ticketing. Free.