[Rt-devel] Need help with RT post upgrade

Janet Houser jhouser at cfa.harvard.edu
Mon Oct 13 19:30:59 EDT 2008


I'm running Centos 5.2 and upgraded from rt 3.6.5 to 3.8.1.  I had the 
same problem and did get around it by
changing my sessions to user files instead of the database but this 
method still fails occassionally and sends the
user back to the login page.  It is very annoying.

When I upgraded, I successfully ran the command:

/opt/rt3/sbin/rt-setup-database --dba root --prompt-for-dba-password 
--action upgrade

mysql db is version 5 (both prior and post upgrade) and didn't have to 
be upgraded using:

	perl etc/upgrade/schema.mysql-4.0-4.1.pl db user pass > sql.queries

Do you happen to know how to fix this problem the "proper" way?

I read and re-read the install instructions and thing I followed 
everything correctly.  Guess I didn't :-).



Panu wrote:
>> Any guidance?   I am in the middle of a weekend upgrade (which I can 
>> revert if needed, but prefer not to)
> Look at earlier messages about the same problem.
> The problem you are having is that you didn't follow UPGRADING.mysql:
> 4) Apply mysql 4.0->4.1 schema changes. RT tarball has script
> etc/upgrade/schema.mysql-4.0-4.1.pl that generates SQL queries to 
> upgrade schema of
> the DB. Run it:
> perl etc/upgrade/schema.mysql-4.0-4.1.pl db user pass > sql.queries
> (I suspect you are using Mysql)
> This should be done even if you already have mysql 5 or 4.1 installed. 
> Better name for the file should be "mysql_schema_upgrade_for_3.8.1" IMO.
> Alternatively you can change your sessions to use files instead of 
> database (or check that the field type is correct for the session table 
> fields, a_session should be longblob)
> Also please note that there's a bug (or there was for me and someone 
> else) that makes the schema file have wrong data in it. Check earlier 
> messages for things to check and fix. Like for example "Several
> multi-character fields were temporarily transformed into type CHAR,
> which truncated them to a single character" and MySQL
> doesn't like the CHARACTER SET directive for a field of type BLOB. These
> lines should probably be changed to specify TEXT instead of BLOB (or you
> could remove the 'CHARACTER SET utf8' directive if you know the fields
> in question are used to store binary data instead of text." (Ole)
> _______________________________________________
> List info: http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel

More information about the Rt-devel mailing list