4.0.2 upgrade to 4.0.5

RT Users
1

I have an RT 4.0.2 box that I’d like to update to the newest
version(4.0.5). Are there any database changes, or anything that I
should watch out for while upgrading? Is there a walk through available
for an upgrade like this? Thanks in advance.

Scott Benson
System Administrator | A1 Networks
Voice: 707-703-1043

For support issues please email support@a-1networks.com or call 707-703-1050

2

I have an RT 4.0.2 box that I’d like to update to the newest
version(4.0.5). Are there any database changes, or anything that I
should watch out for while upgrading? Is there a walk through
available for an upgrade like this? Thanks in advance.

There are database upgrades, as the README specifies, you can run make
upgrade-database and it’ll prompt you for your version.

All of the documentation you need is in the README and the
docs/UPGRADING-4.0 file.

-kevin

3

well, after attempting to update, we’re getting this

* Config file /opt/rt4/etc/RT_SiteConfig.pm is locked

The file isn’t opened by anything, it’s not listed in lsof, no .swp file
or anything. Thanks in advance.

Scott Benson
System Administrator | A1 Networks
Voice: 707-703-1043

For support issues please email support@a-1networks.com or call 707-703-1050On 2/3/12 3:52 PM, Kevin Falcone wrote:

There are database upgrades, as the README specifies, you can run make
upgrade-database and it’ll prompt you for your version.

All of the documentation you need is in the README and the
docs/UPGRADING-4.0 file.

-kevin

4

There are database upgrades, as the README specifies, you can run make
upgrade-database and it’ll prompt you for your version.

All of the documentation you need is in the README and the
docs/UPGRADING-4.0 file.

well, after attempting to update, we’re getting this

  • Config file /opt/rt4/etc/RT_SiteConfig.pm is locked

The file isn’t opened by anything, it’s not listed in lsof, no .swp
file or anything. Thanks in advance.

This implies that your RT has gone into Install mode.
Have you looked in the RT logs? Most of the time, this is because
your database server is unreachable.

-kevin