RT Upgrade from 3.8.8 to 4.0.0 Problem

I’m attempting to upgrade RT from 3.8.8 to 4.0.0. I thought I followed
the steps in the README, in the UPGRADE-4.0, and the UPGRADE-3.8 files,
but I’m running in to the following error message:

ephesus.dartmouth.edu#
/data/websites/rh-libdev/scripts/site-cfg/rh-libdev/env.sh ;
/data/website-packages/libdesign/rt/sbin/rt-setup-database --dba
library_rt --prompt-for-dba-password --action upgrade Modification of a
read-only value attempted at
/usr/local/lib/perl5/site_perl/5.8.9/Net/LDAP/Constant.pm line 13.
Compilation failed in require at
/usr/local/lib/perl5/site_perl/5.8.9/Net/LDAP/Message.pm line 7. BEGIN
failed–compilation aborted at
/usr/local/lib/perl5/site_perl/5.8.9/Net/LDAP/Message.pm line 7.
Compilation failed in require at
/usr/local/lib/perl5/site_perl/5.8.9/Net/LDAP.pm line 13. BEGIN
failed–compilation aborted at
/usr/local/lib/perl5/site_perl/5.8.9/Net/LDAP.pm line 13. Compilation
failed in require at /data/website-
packages/libdesign/rt/sbin/…/local/lib/RT/CurrentUser_Local.pm line
202. BEGIN failed–compilation aborted at /data/website-
packages/libdesign/rt/sbin/…/local/lib/RT/CurrentUser_Local.pm line
202. Compilation failed in require at
/data/website-packages/libdesign/rt/sbin/…/lib/RT/Base.pm line 161.
Compilation failed in require at /data/website-
packages/libdesign/rt/sbin/…/lib/RT/Interface/Web/Session.pm line 53.
BEGIN failed–compilation aborted at /data/website-
packages/libdesign/rt/sbin/…/lib/RT/Interface/Web/Session.pm line 53.
Compilation failed in require at
/data/website-packages/libdesign/rt/sbin/…/lib/RT/Interface/Web.pm line
69. BEGIN failed–compilation aborted at /data/website-
packages/libdesign/rt/sbin/…/lib/RT/Interface/Web.pm line 69.
Compilation failed in require at /data/website-
packages/libdesign/rt/sbin/…/lib/RT/ObjectCustomFieldValue.pm line 54.
BEGIN failed–compilation aborted at /data/website-
packages/libdesign/rt/sbin/…/lib/RT/ObjectCustomFieldValue.pm line 54.
Compilation failed in require at /data/website-
packages/libdesign/rt/sbin/…/lib/RT/ObjectCustomFieldValues.pm line 55.
BEGIN failed–compilation aborted at /data/website-
packages/libdesign/rt/sbin/…/lib/RT/ObjectCustomFieldValues.pm line 55.
Compilation failed in require at
/data/website-packages/libdesign/rt/sbin/…/lib/RT/CustomField.pm line
63. BEGIN failed–compilation aborted at /data/website-
packages/libdesign/rt/sbin/…/lib/RT/CustomField.pm line 63. Compilation
failed in require at
/data/website-packages/libdesign/rt/sbin/…/lib/RT/CustomFields.pm line
73. BEGIN failed–compilation aborted at /data/website-
packages/libdesign/rt/sbin/…/lib/RT/CustomFields.pm line 73.
Compilation failed in require at
/data/website-packages/libdesign/rt/sbin/…/lib/RT/Ticket.pm line 77.
BEGIN failed–compilation aborted at
/data/website-packages/libdesign/rt/sbin/…/lib/RT/Ticket.pm line 77.
Compilation failed in require at
/data/website-packages/libdesign/rt/sbin/…/lib/RT/Tickets.pm line 85.
BEGIN failed–compilation aborted at
/data/website-packages/libdesign/rt/sbin/…/lib/RT/Tickets.pm line 85.
Compilation failed in require at
/data/website-packages/libdesign/rt/sbin/…/lib/RT.pm line 395.

The line that I’m executing comes from the end of the "make upgrade"
process, which supposedly finished without any problems.

Searching through the archive I see a similar issue that required an
upgrade to Authen::ExternalAuth, but that’s a separate file. Any other
suggestions?

thanks,

Robert Hoyle

I’m attempting to upgrade RT from 3.8.8 to 4.0.0. I thought I followed
the steps in the README, in the UPGRADE-4.0, and the UPGRADE-3.8 files,
but I’m running in to the following error message:

The line that I’m executing comes from the end of the "make upgrade"
process, which supposedly finished without any problems.

Searching through the archive I see a similar issue that required an
upgrade to Authen::ExternalAuth, but that’s a separate file. Any other
suggestions?

I believe your options are:

  • Use 4.0.1, not 4.0.0
  • Temporarily disable RT::Authen::ExternalAUth in @Plugins until you
    upgrade it
  • Upgrade RT::Authen::ExternalAuth, since 0.09 works fine with 3.8.8 and
    4.0.1

-kevin

Kevin Falcone <falcone bestpractical.com> writes:

I believe your options are:

  • Use 4.0.1, not 4.0.0
  • Temporarily disable RT::Authen::ExternalAUth in @Plugins until you
    upgrade it
  • Upgrade RT::Authen::ExternalAuth, since 0.09 works fine with 3.8.8 and
    4.0.1

If I do a make upgrade from 4.0.1 on the directory that has 4.0.0, will
that screw up the installation?

Also, RT::Authen::ExternalAUth was not anywhere in the error output
above, which is why I wasn’t sure if it was the same issue or not. I
just came across the ExternalAuth link by searching over the mailing
list archives.

thanks,

Robert

Kevin Falcone <falcone bestpractical.com> writes:

I believe your options are:

  • Use 4.0.1, not 4.0.0
  • Temporarily disable RT::Authen::ExternalAUth in @Plugins until you
    upgrade it
  • Upgrade RT::Authen::ExternalAuth, since 0.09 works fine with 3.8.8 and
    4.0.1

If I do a make upgrade from 4.0.1 on the directory that has 4.0.0, will
that screw up the installation?

No.

Also, RT::Authen::ExternalAUth was not anywhere in the error output
above, which is why I wasn’t sure if it was the same issue or not. I
just came across the ExternalAuth link by searching over the mailing
list archives.

The error is thrown by perl before RT ever has a prayer of throwing a
better error.

It is resolved by running a newer RT, a newer RT-Authen-ExternalAuth
(which is already required for RT4) or possibly by the newest release
of Net::LDAP.

Out of curiousity, why was an old version of RT-Authen-ExternalAuth in
your RT tree? Did you upgrade in-place rather than into a clean
directory?

-kevin

Kevin Falcone <falcone bestpractical.com> writes:

Out of curiousity, why was an old version of RT-Authen-ExternalAuth in
your RT tree? Did you upgrade in-place rather than into a clean
directory?

Yes, this was an upgrade-in-place. I inherited the upgrade from someone
else who did the original install, so I didn’t know what local
customizations had been done and figured that an upgrade would be safer
than a fresh install.

Is this going to be a problem?

I’m noticing some RTFM issues from the database update, namely that it
couldn’t update RTFM because 2.0 was installed. I don’t believe that we
use RTFM at all. Can this error be ignored, or is there a way to nuke
this part of the database so that a fresh install of the most recent
RTFM will work?

thanks,

r.

Processing 3.8.9
setlogsock(): type=‘tcp’: TCP service unavailable at
/usr/local/lib/perl5/site_perl/5.8.9/Log/Dispatch/Syslog.pm line 75
Now inserting data.
[Tue Jul 12 15:16:46 2011] [warning]: Use of uninitialized value in
string eq at
/data/website-packages/libdesign/rt/sbin/…/lib/RT/Template.pm line 627,
<> line 1.
(/data/website-packages/libdesign/rt/sbin/…/lib/RT/Template.pm:627)
[Tue Jul 12 15:16:46 2011] [warning]: Use of uninitialized value in
string eq at
/data/website-packages/libdesign/rt/sbin/…/lib/RT/Template.pm line 627,
<> line 1.
(/data/website-packages/libdesign/rt/sbin/…/lib/RT/Template.pm:627)
[Tue Jul 12 15:16:46 2011] [warning]: Use of uninitialized value in
string eq at
/data/website-packages/libdesign/rt/sbin/…/lib/RT/Template.pm line 627,
<> line 1.
(/data/website-packages/libdesign/rt/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.
[Tue Jul 12 15:17:35 2011] [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:14)
[Tue Jul 12 15:17:35 2011] [error]: We
found RTFM tables in your database. Checking for content.
(./etc/upgrade/3.9.8/content:17)
[Tue Jul 12 15:17:35 2011] [warning]:
DBD::Oracle::db selectall_arrayref failed: ORA-00942: table or view does
not exist (DBD ERROR: error possibly near <> indicator at char 37 in
’SELECT count(
) AS articlecount FROM <>FM_Articles’) [for Statement
"SELECT count(
) AS articlecount FROM FM_Articles"] at
./etc/upgrade/3.9.8/content line 19. (./etc/upgrade/3.9.8/content:19)
Processing 4.0.0rc2
Processing 4.0.0rc4
Now populating database schema.
Processing 4.0.0rc7
Now inserting data.
Processing 4.0.1
Now inserting data.
Done.

Kevin Falcone <falcone bestpractical.com> writes:

Out of curiousity, why was an old version of RT-Authen-ExternalAuth in
your RT tree? Did you upgrade in-place rather than into a clean
directory?

Yes, this was an upgrade-in-place. I inherited the upgrade from someone
else who did the original install, so I didn’t know what local
customizations had been done and figured that an upgrade would be safer
than a fresh install.

Is this going to be a problem?

Please review the top of docs/UPGRADING-4.0 as well as the recent blog
post on upgrading:


Both of which talk about why upgrading into /opt/rt3 is a bad idea.

I’m noticing some RTFM issues from the database update, namely that it
couldn’t update RTFM because 2.0 was installed. I don’t believe that we
use RTFM at all. Can this error be ignored, or is there a way to nuke
this part of the database so that a fresh install of the most recent
RTFM will work?

You must have some of the RTFM tables but not all of them? That’s
truly weird.

As the upgrading documentation covers, RTFM is now built into RT 4 as
Articles. If you don’t use it, just remove all the RTFM tables before
upgrading.

setlogsock(): type=‘tcp’: TCP service unavailable at
/usr/local/lib/perl5/site_perl/5.8.9/Log/Dispatch/Syslog.pm line 75

Also, you appear to have some invalid logging settings

-kevin