we moved our old RT installation to a new server.
old installation:
Debian 4.0
rt-3.4.2
MySQL 5.0
Instead of copying the old binaries to the new server and upgrading them
we made a fresh installation of the binaries (rt-3.8.1) on the new server (Debian 4.0;
MySQL 5.0).
After the upgrade, I had the problems described in UPGRADING.mysql:
multiple login requests
corrupt binaries
We fixed the login problems.
Do I have to apply mysql 4.0->4.1 schema changes to make the binaries work properly,
although the old rt installation was working with MySQL 5.0?
I also read about changing the type in the Database:
we moved our old RT installation to a new server.
old installation:
Debian 4.0
rt-3.4.2
MySQL 5.0
Instead of copying the old binaries to the new server and upgrading them
we made a fresh installation of the binaries (rt-3.8.1) on the new server (Debian 4.0;
MySQL 5.0).
After the upgrade, I had the problems described in UPGRADING.mysql:
multiple login requests
corrupt binaries
We fixed the login problems.
Do I have to apply mysql 4.0->4.1 schema changes to make the binaries work properly,
although the old rt installation was working with MySQL 5.0?
Yes, you MUST. Yes, it was working.
I also read about changing the type in the Database:
After the upgrade, I had the problems described in UPGRADING.mysql:
multiple login requests
corrupt binaries
hi andré
I had the same problem with corrupted attachments after a 3.8.1 upgrade,
I solved this problem yesterday by adding the paramater
“–default-character-set=binary” when I dump the old database and when I
import the dump into the new one.