On Fri, Aug 2, 2013 at 11:32 AM, Kevin Falcone <falc...@bestpractical.com>wrote:
> > I just did my test upgrade from rt 3.8.2 / mysql 5.0.75 to rt 4.0.16 > / mysql 5.5.32 > > but session table still showing myisam. > > $ mysql -e 'use rt4; show create table sessions' > > | sessions | CREATE TABLE `sessions` ( > > `id` varbinary(32) NOT NULL DEFAULT '', > > `a_session` longblob, > > `LastUpdated` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE > CURRENT_TIMESTAMP, > > PRIMARY KEY (`id`) > > ) ENGINE=MyISAM DEFAULT CHARSET=utf8 | > > I guess I can just ALTER the session table now? > > Please show a log of your make upgrade-database step > > One of the steps explicitly drops and recreates the sessions table. ~/src/rt-4.0.16# make upgrade-database /usr/bin/perl -I/opt/rt4/local/lib -I/opt/rt4/lib sbin/rt-setup-database --action upgrade --prompt-for-dba-password In order to create or update your RT database, this script needs to connect to your mysql instance on localhost (port '') as root Please specify that user's database password below. If the user has no database password, just press return. Password: Working with: Type: mysql Host: localhost Port: Name: rt4 User: rt_user DBA: root Enter RT version you're upgrading from: 3.8.2 Going to apply following upgrades: * 3.8.3 * 3.8.4 * 3.8.6 * 3.8.8 * 3.8.9 * 3.9.1 * 3.9.2 * 3.9.3 * 3.9.5 * 3.9.6 * 3.9.7 * 3.9.8 * 4.0.1 * 4.0.3 * 4.0.4 * 4.0.6 * 4.0.9 * 4.0.12 * 4.0.13 Enter RT version if you want to stop upgrade at some point, or leave it blank if you want apply above upgrades: IT'S VERY IMPORTANT TO BACK UP BEFORE THIS STEP Proceed [y/N]:y Processing 3.8.3 Now inserting data. Processing 3.8.4 Now inserting data. Processing 3.8.6 Now inserting data. Processing 3.8.8 Now inserting data. [Fri Aug 2 16:42:55 2013] [warning]: Couldn't set SortOrder: That is already the current value (./etc/upgrade/3.8.8/content:32) [Fri Aug 2 16:42:55 2013] [warning]: Couldn't set SortOrder: That is already the current value (./etc/upgrade/3.8.8/content:32) Processing 3.8.9 Now inserting data. [Fri Aug 2 16:42:58 2013] [warning]: Use of uninitialized value in string eq at /home/iqbala/src/rt-4.0.16/sbin/../lib/RT/Template.pm line 652, <> line 1. (/home/iqbala/src/rt-4.0.16/sbin/../lib/RT/Template.pm:652) [Fri Aug 2 16:42:58 2013] [warning]: Use of uninitialized value in string eq at /home/iqbala/src/rt-4.0.16/sbin/../lib/RT/Template.pm line 652, <> line 1. (/home/iqbala/src/rt-4.0.16/sbin/../lib/RT/Template.pm:652) [Fri Aug 2 16:42:58 2013] [warning]: Use of uninitialized value in string eq at /home/iqbala/src/rt-4.0.16/sbin/../lib/RT/Template.pm line 652, <> line 1. (/home/iqbala/src/rt-4.0.16/sbin/../lib/RT/Template.pm:652) Processing 3.9.1 Now inserting data. [Fri Aug 2 16:43:03 2013] [warning]: Unable to grant ExecuteCode on principal 685493: NSI already has that right (./etc/upgrade/3.9.1/content:63) Processing 3.9.2 Now inserting data. Processing 3.9.3 Now populating database schema. Processing 3.9.5 Now populating database schema. Processing 3.9.6 Now populating database schema. Processing 3.9.7 Now populating database schema. Now inserting data. Processing 3.9.8 Now populating database schema. Now inserting data. [Fri Aug 2 16:46:20 2013] [error]: You appear to be upgrading from RTFM 2.0 - We don't support upgrading this old of an RTFM yet (./etc/upgrade/3.9.8/content:11) [Fri Aug 2 16:46:20 2013] [error]: We found RTFM tables in your database. Checking for content. (./etc/upgrade/3.9.8/content:14) [Fri Aug 2 16:46:20 2013] [error]: You appear to have RTFM Articles. You can upgrade using the etc/upgrade/upgrade-articles script. Read more about it in docs/UPGRADING-4.0 (./etc/upgrade/3.9.8/content:20) Processing 4.0.1 Now inserting data. Processing 4.0.3 Now inserting data. Processing 4.0.4 Now inserting data. Processing 4.0.6 Now populating database schema. Now inserting data. Processing 4.0.9 Now inserting data. Processing 4.0.12 Now populating database schema. Processing 4.0.13 Now populating database schema. Done. root@newwebrt:~/src/rt-4.0.16# -- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing?