RT 3.8.1 Logged out on Search

I recently upgraded to RT 3.8.1, RT-Authen-ExternalAuth-0.06_03 and
RT-Extension-CommandByMail-0.06 from source. I was running RT 3.6.7,
installed over the top of the RT 3.6.5 debian package.

Everything looks pretty good, although I think I see that odd
performance problem with firefox on linux sometimes.

Generally when I search I get logged out, and see this error:

[Fri Nov 7 02:42:54 2008] [error]: Couldn’t get principal for not
loaded object (/opt/rt3/bin/…/lib/RT/User_Overlay.pm:1113)
[Fri Nov 7 02:42:54 2008] [error]: Group::HasMember was called with
an argument that isn’t an RT::Principal or id. It’s (undefined)
(/opt/rt3/bin/…/lib/RT/Group_Overlay.pm:1031)

When I log back in, I get the expected search results page. I’m able
to log in, manipulate tickets just fine. I just get logged out on the
search. Ideas? I’ll look at the source tomorrow I think.

Bryan McLellan

Bryan,

this should be an easy fix that has to do with differences in the RT database you migrated from versus the one you use in 3.8.1. you’ll need to follow these steps

  1. export the database from your old RT
  2. update the schema using the information contained in the UPGRADING.mysql file
  3. update the RT databases using the normal scripts contained in README----- Original Message -----
    From: Bryan McLellan btm@loftninjas.org
    Date: Thursday, November 6, 2008 21:52
    Subject: [rt-users] RT 3.8.1 Logged out on Search
    To: rt-users@lists.bestpractical.com

I recently upgraded to RT 3.8.1, RT-Authen-ExternalAuth-0.06_03 and
RT-Extension-CommandByMail-0.06 from source. I was running RT 3.6.7,
installed over the top of the RT 3.6.5 debian package.

Everything looks pretty good, although I think I see that odd
performance problem with firefox on linux sometimes.

Generally when I search I get logged out, and see this error:

[Fri Nov 7 02:42:54 2008] [error]: Couldn’t get principal
for not
loaded object (/opt/rt3/bin/…/lib/RT/User_Overlay.pm:1113)
[Fri Nov 7 02:42:54 2008] [error]: Group::HasMember was
called with
an argument that isn’t an RT::Principal or id. It’s (undefined)
(/opt/rt3/bin/…/lib/RT/Group_Overlay.pm:1031)

When I log back in, I get the expected search results page. I’m able
to log in, manipulate tickets just fine. I just get logged out
on the
search. Ideas? I’ll look at the source tomorrow I think.

Bryan McLellan


http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly
Media.
Buy a copy at http://rtbook.bestpractical.com

this should be an easy fix that has to do with differences in the RT
database you migrated from versus the one you use in 3.8.1. you’ll need to
follow these steps

  1. export the database from your old RT
  2. update the schema using the information contained in the UPGRADING.mysql
    file
  3. update the RT databases using the normal scripts contained in README

I ran [1] per the README during the upgrade, it all went slick. The
original install of this RT instance was on Debian etch, so it’s
always been in mysql >= 5 so UPGRADING.mysql doesn’t apply.

Per Mike Peachy’s recent post [2] about not running
RT-Authen-ExternalAuth-0.06x, I just got the latest version of 0.07_01
from CPAN here [3], as it wasn’t listed in the available versions for
download, nor was it on CPAN when I installed on Wednesday. Installing
this did not correct the logged out on searches problem however.

Bryan

[1] /opt/rt3/sbin/rt-setup-database --dba root
–prompt-for-dba-password --action upgrade
[2] http://www.gossamer-threads.com/lists/rt/users/80097
[3] http://mirrors.gossamer-threads.com/CPAN/authors/id/Z/ZO/ZORDRAK/RT-Authen-ExternalAuth-0.07_01.tar.gz

what version are you migrating from? im certain UPGRADING.mysql
applies…
it says at line 13/14:

If you’re upgrading RT from versions prior to 3.8.0 then you MUST follow
instructions below.On Fri, 7 Nov 2008, Bryan McLellan wrote:

Date: Fri, 7 Nov 2008 09:49:43 -0800
From: Bryan McLellan btm@loftninjas.org
To: JOHN ROMAN cicero@insightbb.com
Cc: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] RT 3.8.1 Logged out on Search

On Fri, Nov 7, 2008 at 4:03 AM, JOHN ROMAN cicero@insightbb.com wrote:

this should be an easy fix that has to do with differences in the RT
database you migrated from versus the one you use in 3.8.1. you’ll need to
follow these steps

  1. export the database from your old RT
  2. update the schema using the information contained in the UPGRADING.mysql
    file
  3. update the RT databases using the normal scripts contained in README

I ran [1] per the README during the upgrade, it all went slick. The
original install of this RT instance was on Debian etch, so it’s
always been in mysql >= 5 so UPGRADING.mysql doesn’t apply.

Per Mike Peachy’s recent post [2] about not running
RT-Authen-ExternalAuth-0.06x, I just got the latest version of 0.07_01
from CPAN here [3], as it wasn’t listed in the available versions for
download, nor was it on CPAN when I installed on Wednesday. Installing
this did not correct the logged out on searches problem however.

Bryan

[1] /opt/rt3/sbin/rt-setup-database --dba root
–prompt-for-dba-password --action upgrade
[2] http://www.gossamer-threads.com/lists/rt/users/80097
[3] http://mirrors.gossamer-threads.com/CPAN/authors/id/Z/ZO/ZORDRAK/RT-Authen-ExternalAuth-0.07_01.tar.gz


http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

nimbius@sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org

what version are you migrating from? im certain UPGRADING.mysql applies…
it says at line 13/14:

If you’re upgrading RT from versions prior to 3.8.0 then you MUST follow
instructions below.

Thanks John, I missed that RT wasn’t using the collation when it
originally created the database, despite the database version.
Updating the database collation and restarting apache appears to have
corrected the problem while searching.

Since my mysql server was on another host, I copied
schema.mysql-4.0-4.1.pl to that host and ran:

perl schema.mysql-4.0-4.1.pl rtdb root > sql.rtdb
mysql -u root rtdb < sql.rtdb