[rt-users] rt-2.0-to-dumpfile errors

[pdh at bestpractical.com]

Dave Dennis wrote:
> When I ran into similar problems a month ago, they said it was cause
> I had not enlargened max_allowed_packet in my.cnf .

Actually, your problem was completely different, involving the
3.0 import, not the 2.0 export.

> It fails really inelegantly too.  Instead of just iterating over the failed
> attachment and going on, so the admin might be left with a working migration
> minus a couple of attachments, the script stops running at the error,
> which makes migration impossible even if one attachment fails.

The failed attachment is a sign of deeper damage. Not fixing that
is likely to bite you in other ways, too.

There are at least two problems I can think of that cause attachment
creation to fail:

1. max_allowed_packet being too small
2. old version of perl with character encoding bugs

either of those will cause pain if not addressed, regardless of how
attachments are handled at import. When would you rather disover
the damage -- at import, or 6 months down the track?