[rt-users] Upgrade from 3.6.11 to 4.0.4 More Errors

Jared Griffith jared.b.griffith at gmail.com
Fri Nov 18 13:46:04 EST 2011


Here's the entire situation.
I have been tasked with migrating and upgrading our rt system to a new
system, complete with MySQL 5, CentOS 6, and all the latest and greatest.
At this point I have followed the README and the UPGRADING.mysql
documentation and followed everything there.  When running make
upgrade-database the first time, and only upgrading to 3.7.87 after of
course changing the MySQL default character set, I did not receive any
errors.  Once I completed that, then ran the upgrade-mysql-schema.pl part,
I came back to run the make upgrade-database again, and upon doing so got
the following errors:
DB Upgrade Errors:
make upgrade-database
/usr/bin/perl -I/storage/www/rt3/local/lib -I/storage/www/rt3/lib
sbin/rt-setup-database --action upgrade --prompt-for-dba-password
Odd number of elements in anonymous hash at
/home/jared/rt-4.0.4/sbin/../lib/RT/Config.pm line 1071.
Use of uninitialized value $_[8] in anonymous hash ({}) at
/home/jared/rt-4.0.4/sbin/../lib/RT/Config.pm line 1071.
Odd number of elements in hash assignment at
/home/jared/rt-4.0.4/sbin/../lib/RT/Config.pm line 1072.
Use of uninitialized value within @_ in list assignment at
/home/jared/rt-4.0.4/sbin/../lib/RT/Config.pm line 1072.
Subroutine _InitSQL redefined at
/storage/www/rt3/lib/RT/Tickets_Overlay_SQL.pm line 63.
Subroutine _SQLLimit redefined at
/storage/www/rt3/lib/RT/Tickets_Overlay_SQL.pm line 87.
Subroutine _SQLJoin redefined at
/storage/www/rt3/lib/RT/Tickets_Overlay_SQL.pm line 106.
Subroutine _OpenParen redefined at
/storage/www/rt3/lib/RT/Tickets_Overlay_SQL.pm line 116.
Subroutine _CloseParen redefined at
/storage/www/rt3/lib/RT/Tickets_Overlay_SQL.pm line 119.
Subroutine _close_bundle redefined at
/storage/www/rt3/lib/RT/Tickets_Overlay_SQL.pm line 170.
Subroutine _parser redefined at
/storage/www/rt3/lib/RT/Tickets_Overlay_SQL.pm line 201.
Subroutine ClausesToSQL redefined at
/storage/www/rt3/lib/RT/Tickets_Overlay_SQL.pm line 377.
Subroutine FromSQL redefined at
/storage/www/rt3/lib/RT/Tickets_Overlay_SQL.pm line 477.
Subroutine Query redefined at
/storage/www/rt3/lib/RT/Tickets_Overlay_SQL.pm line 543.
In order to create or update your RT database, this script needs to connect
to your  mysql instance on localhost 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
Name: rt3
User: rt_user
DBA: root
Enter RT version you're upgrading from: 3.7.87

Going to apply following upgrades:
* 3.8.0
* 3.8.1
* 3.8.2
* 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.0rc2
* 4.0.0rc4
* 4.0.0rc7
* 4.0.1
* 4.0.3
* 4.0.4

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.0
Now inserting data.
Processing 3.8.1
Now inserting data.
Processing 3.8.2
Now inserting data.
[Fri Nov 18 18:26:20 2011] [warning]: Going to add [OLD] prefix to all
templates in approvals queue. If you have never used approvals, you can
safely delete all the templates with the [OLD] prefix. Leave the new
Approval templates because you may eventually want to start using
approvals. (./etc/upgrade/3.8.2/content:3)
[Fri Nov 18 18:26:21 2011] [warning]: IMPORTANT: We're going to delete all
scrips in Approvals queue and save them in 'rt-approvals-scrips-KyRb' file.
(./etc/upgrade/3.8.2/content:165)
Processing 3.8.3
Now inserting data.
[Fri Nov 18 18:26:27 2011] [error]: Template not found
(/home/jared/rt-4.0.4/sbin/../lib/RT/Handle.pm:1037)
Processing 3.8.4
Now inserting data.
Processing 3.8.6
Now inserting data.
Processing 3.8.8
Now inserting data.
[Fri Nov 18 18:26:44 2011] [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 Nov 18 18:26:50 2011] [warning]: Resolver RT::URI::fsck_com_rt could
not parse fsck.com-rt://gdmxchange.com/ticket/, maybe Organization config
was changed? (/home/jared/rt-4.0.4/sbin/../lib/RT/URI.pm:146)
[Fri Nov 18 18:26:50 2011] [warning]: Use of uninitialized value in string
eq at /home/jared/rt-4.0.4/sbin/../lib/RT/Template.pm line 627, <> line 1.
(/home/jared/rt-4.0.4/sbin/../lib/RT/Template.pm:627)
[Fri Nov 18 18:26:50 2011] [warning]: Use of uninitialized value in string
eq at /home/jared/rt-4.0.4/sbin/../lib/RT/Template.pm line 627, <> line 1.
(/home/jared/rt-4.0.4/sbin/../lib/RT/Template.pm:627)
[Fri Nov 18 18:26:50 2011] [warning]: Use of uninitialized value in string
eq at /home/jared/rt-4.0.4/sbin/../lib/RT/Template.pm line 627, <> line 1.
(/home/jared/rt-4.0.4/sbin/../lib/RT/Template.pm:627)
Processing 3.9.1
Now inserting data.
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.
Processing 4.0.0rc2
Now populating database schema.
Processing 4.0.0rc4
Now populating database schema.
Processing 4.0.0rc7
Now inserting data.
Processing 4.0.1
Now inserting data.
Processing 4.0.3
Now inserting data.
Processing 4.0.4
Now inserting data.
Done.


Is that normal to see those errors?

Also, when restarting the Apache server, I am getting the following errors
from that:
HTTPD Restart
Starting httpd: Odd number of elements in anonymous hash at
/storage/www/rt3/sbin/../lib/RT/Config.pm line 1071.
Use of uninitialized value $_[8] in anonymous hash ({}) at
/storage/www/rt3/sbin/../lib/RT/Config.pm line 1071.
Odd number of elements in hash assignment at
/storage/www/rt3/sbin/../lib/RT/Config.pm line 1072.
Use of uninitialized value within @_ in list assignment at
/storage/www/rt3/sbin/../lib/RT/Config.pm line 1072.

Is that normal as well?

Another fun fact is that I also moved the install from the default /opt to
the /storage location in the error messages.  Would this be causing the
issues even though when I ran the configure I made sure to specify the new
location?




-- 
- Thanks for your time
- Jared B. Griffith
- Email - jared.b.griffith at gmail.com
- Cell Phone - 909-653-7814
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20111118/af5e2290/attachment.htm>


More information about the rt-users mailing list