Upgrade from 3.11 to 3.2 Latest on test system

[p3isys]

Greetings:
We have a production instance of OTRS running in the Amazon Cloud which runs perfectly. I would like to upgrade it to the latest version. In order to get it up to 4.x, if I understand correctly, I need to upgrade first to 3.2, then to 3.3, and then we can jump directly to 4.latest.
The AWS instance is running on Ubuntu, installed from source, and I did the original install.
I took a current manual backup of the database and the /opt/otrs directory from the AWS Ubuntu instance after stopping apache2 and the cron services (postfix is not running - we use Google Apps as the mail engine).

Rather than to try to upgrade the production host directly, I am using a lab system to do the upgrade so I have a good understanding (and more importantly so I don't do anything that affects the production system).

I installed 3.2.latest on the lab box and was able to get it up and working successfully - logons were successful to the generic default installation.

I stopped Apache2 and the cron services on the lab/test box.

I created a new database called otrsdb and restored the database from the production box to this.

Next, I copied over the Config.pm, the DefaultAgent.pm, and the ZZAuto.pm from the source box to the respective locations on the target box with the 3.2 installation. I edited Config.pm to point to the restored database.

At this point we have a vanilla 3.2 installation with the old Config.pm, DefaultAgent.pm, and ZZAuto.pm files from the production 3.11 instance, and the database from the 3.11 instance.

After this, I ran /opt/otrs/bin/otrs.CheckModules.pl (I had done so already during the 3.2 installation, but here again, all was well). I then ran the /opt/bin/otrs.CheckDB.pl script. The default database engine was MyISAM on the production database, so I went into MySQL and listed the table names, then used the table name list to make a script to alter the tables to INNOdb. This ran successfully, and the next otrs.CheckDB.pl script connected and ran properly with no errors.

Next I ran the /opt/otrs/scripts/DBUpdate-to-3.2.pl script. There were errors the script itself said were okay, and it completed prompting that migration was complete.

After this I ran /opt/otrs/bin/otrs.RebuildConfig.pl and /opt/otrs/bin/otrs.DeleteCache.pl successfully, then restarted Apache2 and cron services.

At this point I should have been able to log into the system. The logon screen displays successfully but when I attempted to log on using the primary user account I use, I got Session Invalid. Please log in again. I clicked on the Lost your password? link and got a reset link. The reset message came through normally, but the link had the URL to the production box (not surprisingly, the FQDN is set to the production location). I edited the link and put in the IP address to the lab box. It let me change the password, but even after inputting and verifying the password I am still getting Session invalid. Please log in again.

I think I'm close to getting in - is the Session ID keyed to the FQDN of the OTRS server? If so, then I won't be able to get in until I can change the FQDN to match the IP address of the lab box instead of the URL of the production box. Or am I doing something else wrong?

I have plenty of time - this is on the lab system, and if I need to blow the whole thing away that will be no problem at all. Production remains sacrosanct, and when we get everything updated what I intend to do is to shut down the current instance and provision a new AWS instance to install the new OTRS current version. We will always be able to roll back to the production system that's running currently if we need to, and I have additional snapshots of it, so backup is not a problem. I just want to get everything the way it should be in the lab before I switch to a new production instance, so there is no emergency - it's important to get this done, but not urgent.

Many thanks in advance - and holiday greetings!

Rob in Memphis

[eandrex]

Hi, you forgot an step.

before executing

Code: Select all

DBUpdate-to-3.2.pl

you need to run these queries in your RDBMS

Code: Select all

DBUpdate-to-3.2.xxx.sql

where xxx is your database engine

that file is in your <otrs_home>/scripts folder.

if after that you are still getting errors, you may want to include logs in your post

[p3isys]

Thanks much - that script did not complete properly. The "otrs.dynamic_field" table doesn't exist, and this causes an error when I attempt to execute the script. I will restore the database again and attempt to run the sql script on a clean backup database.
Thanks for your reply,
Rob