Need help with RT post upgrade

I upgraded RT 3.4.5 to 3.8.1

RT comes up and I can see all the tickets.

Every time I select a ticket that I have not yet seen, it goes back to the
authentication screen. I authenticate and then it continues.

Previously accessed tickets do not behave this way.

Any guidance? I am in the middle of a weekend upgrade (which I can revert
if needed, but prefer not to)

I did a previous upgrade from 3.6 to 3.8 at another site and did not have
this issue.

Prior to upgrading, I experimented on this new RT instance with fresh data.
I then dropped that DB and did a make initialize-database. It worked well.

I followed the Upgrade directions for apps and DB.

The main difference is that I loaded a brand new instance of RT on a new
machine.

I then restored the database, ran the database update process, copied over
the RT_Site_Config.pm and used the same apache config file that worked on
the virgin installation.

Bryon

I mis-typed. It appears that every ticket I select asks me to
re-authenticate.

            No errors in RT.log or apache logs.

The only thing I see in the log is

[info]: Successful login for user from nnn.nnn.nnn.nnn
(/opt/rt3/share/html/autohandle:223)From: rt-devel-bounces@lists.bestpractical.com
[mailto:rt-devel-bounces@lists.bestpractical.com] On Behalf Of Bryon Beilman
Sent: Saturday, October 04, 2008 6:52 PM
To: rt-devel@lists.bestpractical.com
Subject: [Rt-devel] Need help with RT post upgrade

I upgraded RT 3.4.5 to 3.8.1

RT comes up and I can see all the tickets.

Every time I select a ticket that I have not yet seen, it goes back to the
authentication screen. I authenticate and then it continues.

Previously accessed tickets do not behave this way.

Any guidance? I am in the middle of a weekend upgrade (which I can revert
if needed, but prefer not to)

I did a previous upgrade from 3.6 to 3.8 at another site and did not have
this issue.

Prior to upgrading, I experimented on this new RT instance with fresh data.
I then dropped that DB and did a make initialize-database. It worked well.

I followed the Upgrade directions for apps and DB.

The main difference is that I loaded a brand new instance of RT on a new
machine.

I then restored the database, ran the database update process, copied over
the RT_Site_Config.pm and used the same apache config file that worked on
the virgin installation.

Bryon

Any guidance? I am in the middle of a weekend upgrade (which I can
revert if needed, but prefer not to)

Look at earlier messages about the same problem.

The problem you are having is that you didn’t follow UPGRADING.mysql:

  1. Apply mysql 4.0->4.1 schema changes. RT tarball has script
    etc/upgrade/schema.mysql-4.0-4.1.pl that generates SQL queries to
    upgrade schema of
    the DB. Run it:

perl etc/upgrade/schema.mysql-4.0-4.1.pl db user pass > sql.queries

(I suspect you are using Mysql)

This should be done even if you already have mysql 5 or 4.1 installed.
Better name for the file should be “mysql_schema_upgrade_for_3.8.1” IMO.

Alternatively you can change your sessions to use files instead of
database (or check that the field type is correct for the session table
fields, a_session should be longblob)

Also please note that there’s a bug (or there was for me and someone
else) that makes the schema file have wrong data in it. Check earlier
messages for things to check and fix. Like for example “Several
multi-character fields were temporarily transformed into type CHAR,
which truncated them to a single character” and MySQL
doesn’t like the CHARACTER SET directive for a field of type BLOB. These
lines should probably be changed to specify TEXT instead of BLOB (or you
could remove the ‘CHARACTER SET utf8’ directive if you know the fields
in question are used to store binary data instead of text." (Ole)

Panu,
Thanks I did a repo search but didn’t find it. I will re-read it. I was
already running mysql 4, so I didn’t think it applied to me. I will go back
and approach it from ground up. I had to revert back to the previous
instance, but will retry it using the information below.

Thank you,
I will report back on this and I may even try to improve the installation
instructions as I go along and share them back.From: rt-devel-bounces@lists.bestpractical.com
[mailto:rt-devel-bounces@lists.bestpractical.com] On Behalf Of Panu
Sent: Monday, October 06, 2008 2:59 AM
To: rt-devel@lists.bestpractical.com
Subject: Re: [Rt-devel] Need help with RT post upgrade

Any guidance? I am in the middle of a weekend upgrade (which I can
revert if needed, but prefer not to)

Look at earlier messages about the same problem.

The problem you are having is that you didn’t follow UPGRADING.mysql:

  1. Apply mysql 4.0->4.1 schema changes. RT tarball has script
    etc/upgrade/schema.mysql-4.0-4.1.pl that generates SQL queries to
    upgrade schema of
    the DB. Run it:

perl etc/upgrade/schema.mysql-4.0-4.1.pl db user pass > sql.queries

(I suspect you are using Mysql)

This should be done even if you already have mysql 5 or 4.1 installed.
Better name for the file should be “mysql_schema_upgrade_for_3.8.1” IMO.

Alternatively you can change your sessions to use files instead of
database (or check that the field type is correct for the session table
fields, a_session should be longblob)

Also please note that there’s a bug (or there was for me and someone
else) that makes the schema file have wrong data in it. Check earlier
messages for things to check and fix. Like for example “Several
multi-character fields were temporarily transformed into type CHAR,
which truncated them to a single character” and MySQL
doesn’t like the CHARACTER SET directive for a field of type BLOB. These
lines should probably be changed to specify TEXT instead of BLOB (or you
could remove the ‘CHARACTER SET utf8’ directive if you know the fields
in question are used to store binary data instead of text." (Ole)
List info: http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel

Hi,

I’m running Centos 5.2 and upgraded from rt 3.6.5 to 3.8.1. I had the
same problem and did get around it by
changing my sessions to user files instead of the database but this
method still fails occassionally and sends the
user back to the login page. It is very annoying.

When I upgraded, I successfully ran the command:

/opt/rt3/sbin/rt-setup-database --dba root --prompt-for-dba-password
–action upgrade

mysql db is version 5 (both prior and post upgrade) and didn’t have to
be upgraded using:

perl etc/upgrade/schema.mysql-4.0-4.1.pl db user pass > sql.queries

Do you happen to know how to fix this problem the “proper” way?

I read and re-read the install instructions and thing I followed
everything correctly. Guess I didn’t :-).

thanks.

janet

Panu wrote:

Janet Houser wrote:

Hi,

I’m running Centos 5.2 and upgraded from rt 3.6.5 to 3.8.1. I had the
same problem and did get around it by
changing my sessions to user files instead of the database but this
method still fails occassionally and sends the
user back to the login page. It is very annoying.

Sorry I don’t have ideas if you are already using files for sessions,
the database change just updates the database to be able to handle
session data (among other things). Maybe there’s some other change the
schema upgrade takes care of?

When I upgraded, I successfully ran the command:

/opt/rt3/sbin/rt-setup-database --dba root --prompt-for-dba-password
–action upgrade

mysql db is version 5 (both prior and post upgrade) and didn’t have to
be upgraded using:

perl etc/upgrade/schema.mysql-4.0-4.1.pl db user pass > sql.queries

Do you happen to know how to fix this problem the “proper” way?

Answer below:

This should be done even if you already have mysql 5 or 4.1 installed.
Better name for the file should be “mysql_schema_upgrade_for_3.8.1” IMO.

If you upgrade from version below 3.8 and use Mysql you have to use the
method describe above.

The schema script has some bugs so make sure you check the things it
suggests changing (and better yet try to understand what they mean,
luckily I got help pointing the errors for me probably saving some time
and frustration)

Hi Panu,

mysql db is version 5 (both prior and post upgrade) and didn’t have to
be upgraded using:

perl etc/upgrade/schema.mysql-4.0-4.1.pl db user pass > sql.queries

Do you happen to know how to fix this problem the “proper” way?

Answer below:

This should be done even if you already have mysql 5 or 4.1
installed. Better name for the file should be
"mysql_schema_upgrade_for_3.8.1" IMO.

Yeah, I tried this and it gave me errors and wouldn’t run. That is why
I thought I didn’t need it with mysql vs. 5.

If you upgrade from version below 3.8 and use Mysql you have to use the
method describe above.

The schema script has some bugs so make sure you check the things it
suggests changing (and better yet try to understand what they mean,
luckily I got help pointing the errors for me probably saving some time
and frustration)

Thanks for your help.

j

Hi Panu,

mysql db is version 5 (both prior and post upgrade) and didn’t have to
be upgraded using:

perl etc/upgrade/schema.mysql-4.0-4.1.pl db user pass > sql.queries

Do you happen to know how to fix this problem the “proper” way?

Answer below:

This should be done even if you already have mysql 5 or 4.1
installed. Better name for the file should be
"mysql_schema_upgrade_for_3.8.1" IMO.

Yeah, I tried this and it gave me errors and wouldn’t run. That is why
I thought I didn’t need it with mysql vs. 5.
Have you reported those errors?

If you upgrade from version below 3.8 and use Mysql you have to use the
method describe above.

The schema script has some bugs so make sure you check the things it
suggests changing (and better yet try to understand what they mean,
luckily I got help pointing the errors for me probably saving some time
and frustration)

Thanks for your help.

j


List info: http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel

Best regards, Ruslan.

Ruslan Zakirov wrote:

Hi Panu,

mysql db is version 5 (both prior and post upgrade) and didn’t have to
be upgraded using:

perl etc/upgrade/schema.mysql-4.0-4.1.pl db user pass > sql.queries

Do you happen to know how to fix this problem the “proper” way?

Answer below:

This should be done even if you already have mysql 5 or 4.1
installed. Better name for the file should be
"mysql_schema_upgrade_for_3.8.1" IMO.

Yeah, I tried this and it gave me errors and wouldn’t run. That is why
I thought I didn’t need it with mysql vs. 5.

Have you reported those errors?

No. I wanted to see if it was something in the script that I could fix first but
I haven’t had a chance to look into this.

From the UPGRADING.mysql file in rt-3.8.1, it says:

=== Upgrading RT from versions prior to 3.8.0 ===

  1. Apply mysql 4.0->4.1 schema changes. RT tarball has script
    etc/upgrade/schema.mysql-4.0-4.1.pl that generates SQL queries to upgrade schema of
    the DB. Run it:

    perl etc/upgrade/schema.mysql-4.0-4.1.pl db user pass > sql.queries

When I ran this command, I got the error:

[root@rt rt-3.8.1]# perl etc/upgrade/schema.mysql-4.0-4.1.pl db user pass (using db=rt3 and user=root or rt_user)
DBD::mysql version 4.002 required–this is only version 3.0007 at etc/upgrade/schema.mysql-4.0-4.1.pl line 7.
BEGIN failed–compilation aborted at etc/upgrade/schema.mysql-4.0-4.1.pl line 7.

[root@rt rt-3.8.1]# mysql --version
mysql Ver 14.12 Distrib 5.0.45, for redhat-linux-gnu (i686) using readline 5.0

[root@rt rt-3.8.1]# cat /etc/redhat-release
CentOS release 5.2 (Final)

I don’t quite understand the error. This is a fresh install of centos and I followed the upgrade
procedures. I assumed since it was for mysql-4.0 and 4.1 that the error resulted from the fact
that I have mysql vs. 5.0.45. However, Panu suggested that it should also be run for
mysql vs. 5.

thanks.

janet

If you upgrade from version below 3.8 and use Mysql you have to use the
method describe above.

The schema script has some bugs so make sure you check the things it
suggests changing (and better yet try to understand what they mean,
luckily I got help pointing the errors for me probably saving some time
and frustration)

Thanks for your help.

j


List info: http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel


Spam detection software, running on the system “raincoat.cfa.harvard.edu”, has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn’t spam) or label
similar future email. If you have any questions, see
fst@ipa.harvard.edu for details.

wrote: > Hi Panu, > >>> >>> mysql db is version 5 (both prior and post upgrade)
and didn’t have to >>> be upgraded using: >>> >>> perl etc/upgrade/schema.mysql-4.0-4.1.pl
db user pass > sql.queries >>> >>> Do you happen to know how to fix this
problem the “proper” way? >> >> Answer below: >> >>>> This should be done
even if you already have mysql 5 or 4.1 >>>> installed. Better name for the
file should be >>>> “mysql_schema_upgrade_for_3.8.1” IMO. > > > Yeah, I tried
this and it gave me errors and wouldn’t run. That is why > I thought I didn’t
need it with mysql vs. 5. Have you reported those errors? […]

Content analysis details: (4.8 points, 4.0 required)

pts rule name description


1.4 SPF_NEUTRAL SPF: sender does not match SPF record (neutral)
[SPF failed: Please see http://www.openspf.org/why.html?sender=ruslan.zakirov%40gmail.com&ip=131.142.41.8&receiver=raincoat.cfa.harvard.edu]
2.0 DNS_FROM_SECURITYSAGE RBL: Envelope sender in
blackholes.securitysage.com
1.4 DNS_FROM_RFC_POST RBL: Envelope sender in postmaster.rfc-ignorant.org

Dr. Janet L. Houser
Chandra X-ray Observatory
Smithsonian Astrophysical Observatory
Mail Stop 33
60 Garden Street
Cambridge, MA 02138
E-mail: jhouser@cfa.harvard.edu
Telephone: 617-496-7082
Fax: 617-496-7049

Ruslan Zakirov wrote:

Hi Panu,

mysql db is version 5 (both prior and post upgrade) and didn’t have to
be upgraded using:

perl etc/upgrade/schema.mysql-4.0-4.1.pl db user pass > sql.queries

Do you happen to know how to fix this problem the “proper” way?

Answer below:

This should be done even if you already have mysql 5 or 4.1
installed. Better name for the file should be
"mysql_schema_upgrade_for_3.8.1" IMO.

Yeah, I tried this and it gave me errors and wouldn’t run. That is why
I thought I didn’t need it with mysql vs. 5.

Have you reported those errors?

No. I wanted to see if it was something in the script that I could fix first but
I haven’t had a chance to look into this.

From the UPGRADING.mysql file in rt-3.8.1, it says:

=== Upgrading RT from versions prior to 3.8.0 ===

  1. Apply mysql 4.0->4.1 schema changes. RT tarball has script
    etc/upgrade/schema.mysql-4.0-4.1.pl that generates SQL queries to upgrade schema of
    the DB. Run it:

    perl etc/upgrade/schema.mysql-4.0-4.1.pl db user pass > sql.queries

When I ran this command, I got the error:

[root@rt rt-3.8.1]# perl etc/upgrade/schema.mysql-4.0-4.1.pl db user pass (using db=rt3 and user=root or rt_user)
DBD::mysql version 4.002 required–this is only version 3.0007 at etc/upgrade/schema.mysql-4.0-4.1.pl line 7.
BEGIN failed–compilation aborted at etc/upgrade/schema.mysql-4.0-4.1.pl line 7.

[root@rt rt-3.8.1]# mysql --version
mysql Ver 14.12 Distrib 5.0.45, for redhat-linux-gnu (i686) using readline 5.0

[root@rt rt-3.8.1]# cat /etc/redhat-release
CentOS release 5.2 (Final)

I don’t quite understand the error. This is a fresh install of centos and I followed the upgrade
procedures. I assumed since it was for mysql-4.0 and 4.1 that the error resulted from the fact
that I have mysql vs. 5.0.45. However, Panu suggested that it should also be run for
mysql vs. 5.

thanks.

janet

If you upgrade from version below 3.8 and use Mysql you have to use the
method describe above.

The schema script has some bugs so make sure you check the things it
suggests changing (and better yet try to understand what they mean,
luckily I got help pointing the errors for me probably saving some time
and frustration)

Thanks for your help.

j


List info: http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel


Spam detection software, running on the system “raincoat.cfa.harvard.edu”, has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn’t spam) or label
similar future email. If you have any questions, see
fst@ipa.harvard.edu for details.

wrote: > Hi Panu, > >>> >>> mysql db is version 5 (both prior and post upgrade)
and didn’t have to >>> be upgraded using: >>> >>> perl etc/upgrade/schema.mysql-4.0-4.1.pl
db user pass > sql.queries >>> >>> Do you happen to know how to fix this
problem the “proper” way? >> >> Answer below: >> >>>> This should be done
even if you already have mysql 5 or 4.1 >>>> installed. Better name for the
file should be >>>> “mysql_schema_upgrade_for_3.8.1” IMO. > > > Yeah, I tried
this and it gave me errors and wouldn’t run. That is why > I thought I didn’t
need it with mysql vs. 5. Have you reported those errors? […]

Content analysis details: (4.8 points, 4.0 required)

pts rule name description


1.4 SPF_NEUTRAL SPF: sender does not match SPF record (neutral)
[SPF failed: Please see http://www.openspf.org/why.html?sender=ruslan.zakirov%40gmail.com&ip=131.142.41.8&receiver=raincoat.cfa.harvard.edu]
2.0 DNS_FROM_SECURITYSAGE RBL: Envelope sender in
blackholes.securitysage.com
1.4 DNS_FROM_RFC_POST RBL: Envelope sender in postmaster.rfc-ignorant.org


Dr. Janet L. Houser
Chandra X-ray Observatory
Smithsonian Astrophysical Observatory
Mail Stop 33
60 Garden Street
Cambridge, MA 02138
E-mail: jhouser@cfa.harvard.edu
Telephone: 617-496-7082
Fax: 617-496-7049


List info: http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel

The problem isn’t your MySQL version, it’s your DBD::mysql (perl
module) version. You need to upgrade that to version >= 4.002

-Jacob

Ruslan Zakirov wrote:

Hi Panu,

mysql db is version 5 (both prior and post upgrade) and didn’t have to
be upgraded using:

perl etc/upgrade/schema.mysql-4.0-4.1.pl db user pass > sql.queries

Do you happen to know how to fix this problem the “proper” way?

Answer below:

This should be done even if you already have mysql 5 or 4.1
installed. Better name for the file should be
"mysql_schema_upgrade_for_3.8.1" IMO.

Yeah, I tried this and it gave me errors and wouldn’t run. That is why
I thought I didn’t need it with mysql vs. 5.

Have you reported those errors?

No. I wanted to see if it was something in the script that I could fix
first but
I haven’t had a chance to look into this.

From the UPGRADING.mysql file in rt-3.8.1, it says:

=== Upgrading RT from versions prior to 3.8.0 ===

  1. Apply mysql 4.0->4.1 schema changes. RT tarball has script
    etc/upgrade/schema.mysql-4.0-4.1.pl that generates SQL queries to upgrade
    schema of
    the DB. Run it:

    perl etc/upgrade/schema.mysql-4.0-4.1.pl db user pass > sql.queries

When I ran this command, I got the error:

[root@rt rt-3.8.1]# perl etc/upgrade/schema.mysql-4.0-4.1.pl db user pass
(using db=rt3 and user=root or rt_user)
DBD::mysql version 4.002 required–this is only version 3.0007 at
etc/upgrade/schema.mysql-4.0-4.1.pl line 7.
BEGIN failed–compilation aborted at etc/upgrade/schema.mysql-4.0-4.1.pl
line 7.

run:

perl -e ‘use DBD::mysql 4.002’

DBD::mysql is a perl driver for mysql, it’s a module available from
the CPAN. You can install it using ‘cpan’ program, from sources or
using packaging system of your distro, however your distribution most
probably has very old version of the driver.

Installing it from sources or via cpan can be a challenge for
unexperienced admins as perl modules usually make autotests. In this
case you’ll need compiler as module has parts written in C, headers
for mysql-client libraries, a live mysql server with a DB to test
against and some user to test with.

Some people may suggest you ignore test step or its failures, but it’s
direct way to shoot your leg with exit point in your head. Don’t panic
if tests fail. Make sure you’ve done them right and report whole log
via http://rt.cpan.org (almost all perl modules has a queue there) so
authors can fix it later. Then install newer DBI module, it’s a perl
abstract database interface that make it possible to talk to many DBs
using the same API. All DBD::* drivers are extensions for DBI and
there is close interconnection between version of DBI module and any
DBD::* driver. I don’t know why, but mysql developers don’t want to
increase requirement on version of DBI module. Anyway experience shows
that it’s better to use newer DBI with newer DBD::mysql as developers
often use the latest versions and have no resources to test against
older versions.

It could sound scary, but it’s actually easy.

[root@rt rt-3.8.1]# mysql --version
mysql Ver 14.12 Distrib 5.0.45, for redhat-linux-gnu (i686) using readline
5.0

[root@rt rt-3.8.1]# cat /etc/redhat-release
CentOS release 5.2 (Final)

I don’t quite understand the error. This is a fresh install of centos and I
followed the upgrade
procedures. I assumed since it was for mysql-4.0 and 4.1 that the error
resulted from the fact
that I have mysql vs. 5.0.45. However, Panu suggested that it should also
be run for
mysql vs. 5.

thanks.

janet

If you upgrade from version below 3.8 and use Mysql you have to use the
method describe above.

The schema script has some bugs so make sure you check the things it
suggests changing (and better yet try to understand what they mean,
luckily I got help pointing the errors for me probably saving some time
and frustration)

Thanks for your help.

j


List info:
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel


Spam detection software, running on the system “raincoat.cfa.harvard.edu”,
has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn’t spam) or label
similar future email. If you have any questions, see
fst@ipa.harvard.edu for details.

Content preview: On Tue, Oct 14, 2008 at 4:11 PM, Janet L. Houser
jhouser@cfa.harvard.edu
wrote: > Hi Panu, > >>> >>> mysql db is version 5 (both prior and post
upgrade)
and didn’t have to >>> be upgraded using: >>> >>> perl
etc/upgrade/schema.mysql-4.0-4.1.pl
db user pass > sql.queries >>> >>> Do you happen to know how to fix this
problem the “proper” way? >> >> Answer below: >> >>>> This should be done
even if you already have mysql 5 or 4.1 >>>> installed. Better name for
the
file should be >>>> “mysql_schema_upgrade_for_3.8.1” IMO. > > > Yeah, I
tried
this and it gave me errors and wouldn’t run. That is why > I thought I
didn’t
need it with mysql vs. 5. Have you reported those errors? […]
Content analysis details: (4.8 points, 4.0 required)

pts rule name description



1.4 SPF_NEUTRAL SPF: sender does not match SPF record
(neutral)
[SPF failed: Please see
http://www.openspf.org/why.html?sender=ruslan.zakirov%40gmail.com&ip=131.142.41.8&receiver=raincoat.cfa.harvard.edu]
2.0 DNS_FROM_SECURITYSAGE RBL: Envelope sender in
blackholes.securitysage.com
1.4 DNS_FROM_RFC_POST RBL: Envelope sender in
postmaster.rfc-ignorant.org


Dr. Janet L. Houser
Chandra X-ray Observatory
Smithsonian Astrophysical Observatory
Mail Stop 33
60 Garden Street
Cambridge, MA 02138
E-mail: jhouser@cfa.harvard.edu
Telephone: 617-496-7082
Fax: 617-496-7049

Best regards, Ruslan.

Thanks folks!

I’ll give this a try.

Cheers,

j

Jacob Helwig wrote:> On Wed, Oct 15, 2008 at 12:05, Janet Houser jhouser@cfa.harvard.edu wrote:

Ruslan Zakirov wrote:

On Tue, Oct 14, 2008 at 4:11 PM, Janet L. Houser jhouser@cfa.harvard.edu wrote:

Hi Panu,

mysql db is version 5 (both prior and post upgrade) and didn’t have to
be upgraded using:

perl etc/upgrade/schema.mysql-4.0-4.1.pl db user pass > sql.queries

Do you happen to know how to fix this problem the “proper” way?

Answer below:

This should be done even if you already have mysql 5 or 4.1
installed. Better name for the file should be
"mysql_schema_upgrade_for_3.8.1" IMO.

Yeah, I tried this and it gave me errors and wouldn’t run. That is why
I thought I didn’t need it with mysql vs. 5.

Have you reported those errors?

No. I wanted to see if it was something in the script that I could fix first but
I haven’t had a chance to look into this.

From the UPGRADING.mysql file in rt-3.8.1, it says:

=== Upgrading RT from versions prior to 3.8.0 ===

  1. Apply mysql 4.0->4.1 schema changes. RT tarball has script
    etc/upgrade/schema.mysql-4.0-4.1.pl that generates SQL queries to upgrade schema of
    the DB. Run it:

    perl etc/upgrade/schema.mysql-4.0-4.1.pl db user pass > sql.queries

When I ran this command, I got the error:

[root@rt rt-3.8.1]# perl etc/upgrade/schema.mysql-4.0-4.1.pl db user pass (using db=rt3 and user=root or rt_user)
DBD::mysql version 4.002 required–this is only version 3.0007 at etc/upgrade/schema.mysql-4.0-4.1.pl line 7.
BEGIN failed–compilation aborted at etc/upgrade/schema.mysql-4.0-4.1.pl line 7.

[root@rt rt-3.8.1]# mysql --version
mysql Ver 14.12 Distrib 5.0.45, for redhat-linux-gnu (i686) using readline 5.0

[root@rt rt-3.8.1]# cat /etc/redhat-release
CentOS release 5.2 (Final)

I don’t quite understand the error. This is a fresh install of centos and I followed the upgrade
procedures. I assumed since it was for mysql-4.0 and 4.1 that the error resulted from the fact
that I have mysql vs. 5.0.45. However, Panu suggested that it should also be run for
mysql vs. 5.

thanks.

janet

If you upgrade from version below 3.8 and use Mysql you have to use the
method describe above.

The schema script has some bugs so make sure you check the things it
suggests changing (and better yet try to understand what they mean,
luckily I got help pointing the errors for me probably saving some time
and frustration)

Thanks for your help.

j


List info: http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel


Spam detection software, running on the system “raincoat.cfa.harvard.edu”, has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn’t spam) or label
similar future email. If you have any questions, see
fst@ipa.harvard.edu for details.

Content preview: On Tue, Oct 14, 2008 at 4:11 PM, Janet L. Houser jhouser@cfa.harvard.edu
wrote: > Hi Panu, > >>> >>> mysql db is version 5 (both prior and post upgrade)
and didn’t have to >>> be upgraded using: >>> >>> perl etc/upgrade/schema.mysql-4.0-4.1.pl
db user pass > sql.queries >>> >>> Do you happen to know how to fix this
problem the “proper” way? >> >> Answer below: >> >>>> This should be done
even if you already have mysql 5 or 4.1 >>>> installed. Better name for the
file should be >>>> “mysql_schema_upgrade_for_3.8.1” IMO. > > > Yeah, I tried
this and it gave me errors and wouldn’t run. That is why > I thought I didn’t
need it with mysql vs. 5. Have you reported those errors? […]

Content analysis details: (4.8 points, 4.0 required)

pts rule name description


1.4 SPF_NEUTRAL SPF: sender does not match SPF record (neutral)
[SPF failed: Please see http://www.openspf.org/why.html?sender=ruslan.zakirov%40gmail.com&ip=131.142.41.8&receiver=raincoat.cfa.harvard.edu]
2.0 DNS_FROM_SECURITYSAGE RBL: Envelope sender in
blackholes.securitysage.com
1.4 DNS_FROM_RFC_POST RBL: Envelope sender in postmaster.rfc-ignorant.org


Dr. Janet L. Houser
Chandra X-ray Observatory
Smithsonian Astrophysical Observatory
Mail Stop 33
60 Garden Street
Cambridge, MA 02138
E-mail: jhouser@cfa.harvard.edu
Telephone: 617-496-7082
Fax: 617-496-7049


List info: http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel

The problem isn’t your MySQL version, it’s your DBD::mysql (perl
module) version. You need to upgrade that to version >= 4.002

-Jacob


Spam detection software, running on the system “raincoat.cfa.harvard.edu”, has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn’t spam) or label
similar future email. If you have any questions, see
fst@ipa.harvard.edu for details.

Content preview: On Wed, Oct 15, 2008 at 12:05, Janet Houser jhouser@cfa.harvard.edu
wrote: > > > Ruslan Zakirov wrote: >> On Tue, Oct 14, 2008 at 4:11 PM, Janet
L. Houser >> jhouser@cfa.harvard.edu wrote: >> >>>Hi Panu, >>> >>> >>>>>mysql
db is version 5 (both prior and post upgrade) and didn’t have to >>>>>be
upgraded using: >>>>> >>>>> perl etc/upgrade/schema.mysql-4.0-4.1.pl db user
pass > sql.queries >>>>> >>>>>Do you happen to know how to fix this problem
the “proper” way? >>>> >>>>Answer below: >>>> >>>> >>>>>>This should be done
even if you already have mysql 5 or 4.1 >>>>>>installed. Better name for
the file should be >>>>>>“mysql_schema_upgrade_for_3.8.1” IMO. >>> >>> >>>Yeah,
I tried this and it gave me errors and wouldn’t run. That is why >>>I thought
I didn’t need it with mysql vs. 5. >> >> Have you reported those errors?

No. I wanted to see if it was something in the script that I could fix
first but > I haven’t had a chance to look into this. > > > From the UPGRADING.mysql
file in rt-3.8.1, it says: > > >=== Upgrading RT from versions prior to 3.8.0
=== > > > >4) Apply mysql 4.0->4.1 schema changes. RT tarball has script

etc/upgrade/schema.mysql-4.0-4.1.pl that generates SQL queries to upgrade
schema of > >the DB. Run it: > > > > perl etc/upgrade/schema.mysql-4.0-4.1.pl
db user pass > sql.queries > > When I ran this command, I got the error:

[root@rt rt-3.8.1]# perl etc/upgrade/schema.mysql-4.0-4.1.pl db user pass
(using db=rt3 and user=root or rt_user) > DBD::mysql version 4.002 required–this
is only version 3.0007 at etc/upgrade/schema.mysql-4.0-4.1.pl line 7. > BEGIN
failed–compilation aborted at etc/upgrade/schema.mysql-4.0-4.1.pl line 7.

[root@rt rt-3.8.1]# mysql --version > mysql Ver 14.12 Distrib 5.0.45,
for redhat-linux-gnu (i686) using readline 5.0 > > [root@rt rt-3.8.1]# cat
/etc/redhat-release > CentOS release 5.2 (Final) > > I don’t quite understand
the error. This is a fresh install of centos and I followed the upgrade >
procedures. I assumed since it was for mysql-4.0 and 4.1 that […]

Content analysis details: (4.8 points, 4.0 required)

pts rule name description


1.4 SPF_NEUTRAL SPF: sender does not match SPF record (neutral)
[SPF failed: Please see http://www.openspf.org/why.html?sender=jacob.helwig%40gmail.com&ip=131.142.41.8&receiver=raincoat.cfa.harvard.edu]
2.0 DNS_FROM_SECURITYSAGE RBL: Envelope sender in
blackholes.securitysage.com
1.4 DNS_FROM_RFC_POST RBL: Envelope sender in postmaster.rfc-ignorant.org

Dr. Janet L. Houser
Chandra X-ray Observatory
Smithsonian Astrophysical Observatory
Mail Stop 33
60 Garden Street
Cambridge, MA 02138
E-mail: jhouser@cfa.harvard.edu
Telephone: 617-496-7082
Fax: 617-496-7049