After installing a new version of RT, I’ve noticed that whenever I click
"Tickets" or interact with the query builder such that it reloads the
page, it logs me out. I still remembers it’s state after I log back in,
but this is extremely annoying.
Has anyone else had this problem?
Please let me know if there’s any other information you need.
–Buck
So you think it’s in regard to upgrading?
I’ll try with a fresh database and let you know how it goes.
–Buck-----Original Message-----
From: Trenton Taylor [mailto:trentt@ssi-invest.com]
Sent: Thursday, September 11, 2008 10:26 AM
To: Golemon, Buck
Subject: RE: [rt-users] RT 3.8.1: “Tickets” interface logs you
out
A bunch of us have the issue but it's being ignored on the lists
…
I think jesse considers it our problem for not upgrading
correctly.
I upgraded from rt 3.6.6 to 3.8.0 and ran the upgrade script at
the end of the install … no errors and no “log out” issues in the
interface
I then upgraded from 3.8.0 to 3.8.1 and ran the upgrade script
that was mentioned at the end of the install … no errors but am logged
out on some web clicks.
I went back to 3.8.0 and don't have any problems now ...
Did you follow the UPGRADING.mysql document? I got errors when
trying it.
Nobody has responded to me on the list ..
From: rt-users-bounces@lists.bestpractical.com
[mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of Golemon,
Buck
Sent: Thursday, September 11, 2008 9:17 AM
To: rt-users@bestpractical.com
Subject: [rt-users] RT 3.8.1: “Tickets” interface logs you out
After installing a new version of RT, I've noticed that whenever
I click “Tickets” or interact with the query builder such that it
reloads the page, it logs me out. I still remembers it’s state after I
log back in, but this is extremely annoying.
Has anyone else had this problem?
Please let me know if there's any other information you need.
--Buck
Important: The information contained in this e-mail message is
confidential and is intended only for the named addressee(s). If the
reader of this e-mail message is not an intended recipient (or the
individual responsible for the delivery of this e-mail message to an
intended recipient), please be advised that any re-use, dissemination,
distribution or copying of this e-mail message is prohibited. If you
have received this e-mail message in error, please reply to the sender
that you have received the message in error and then delete it. Thank
you.
No virus found in this incoming message.
Checked by AVG - http://www.avg.com
Version: 8.0.169 / Virus Database: 270.6.19/1664 - Release Date:
2008-09-10 7:00 PM
I may be way off here (I’m a total newbie). But Todd Green wrote this a
couple days ago - might this help?
Just hit and fixed this issue yesterday. My solution was to was to add
the following to
etc/RT_SiteConfig.pmSet($WebSessionClass , ‘Apache::Session::File’);
When I asked him what it was actually doing, this is what he said:
In my digging I determined that by default the sessions are being written
to the SQL database. Notes from others having similar issues >indicated
this might be part of the issue. My current production environment (3.4.2)
writes the sessions to files instead of to the >database so I used the same
option in the new environment as well.
Sorry if that’s not helpful.
-ChrisOn Thu, Sep 11, 2008 at 1:30 PM, Golemon, Buck Buck.Golemon@amd.com wrote:
So you think it’s in regard to upgrading?
I’ll try with a fresh database and let you know how it goes.–Buck
-----Original Message-----
From: Trenton Taylor [mailto:trentt@ssi-invest.com]
Sent: Thursday, September 11, 2008 10:26 AM
To: Golemon, Buck
Subject: RE: [rt-users] RT 3.8.1: “Tickets” interface logs you outA bunch of us have the issue but it’s being ignored on the lists …
I think jesse considers it our problem for not upgrading correctly.
I upgraded from rt 3.6.6 to 3.8.0 and ran the upgrade script at the end of
the install … no errors and no “log out” issues in the interfaceI then upgraded from 3.8.0 to 3.8.1 and ran the upgrade script that was
mentioned at the end of the install … no errors but am logged out on some
web clicks.I went back to 3.8.0 and don’t have any problems now …
Did you follow the UPGRADING.mysql document? I got errors when trying it.
Nobody has responded to me on the list …
From: rt-users-bounces@lists.bestpractical.com [mailto:
rt-users-bounces@lists.bestpractical.com] *On Behalf Of *Golemon, Buck
Sent: Thursday, September 11, 2008 9:17 AM
To: rt-users@bestpractical.com
Subject: [rt-users] RT 3.8.1: “Tickets” interface logs you outAfter installing a new version of RT, I’ve noticed that whenever I click
“Tickets” or interact with the query builder such that it reloads the page,
it logs me out. I still remembers it’s state after I log back in, but this
is extremely annoying.Has anyone else had this problem?
Please let me know if there’s any other information you need.
–Buck
Important: The information contained in this e-mail message is confidential
and is intended only for the named addressee(s). If the reader of this
e-mail message is not an intended recipient (or the individual responsible
for the delivery of this e-mail message to an intended recipient), please be
advised that any re-use, dissemination, distribution or copying of this
e-mail message is prohibited. If you have received this e-mail message in
error, please reply to the sender that you have received the message in
error and then delete it. Thank you.No virus found in this incoming message.
Checked by AVG - http://www.avg.com
Version: 8.0.169 / Virus Database: 270.6.19/1664 - Release Date: 2008-09-10
7:00 PM
Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.comDiscover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
I may be way off here (I’m a total newbie). But Todd Green wrote
this a couple days ago - might this help?Just hit and fixed this issue yesterday. My solution was to was
to add
the following to
etc/RT_SiteConfig.pmSet($WebSessionClass , ‘Apache::Session::File’);
I have to say that this worked for me as well. Although I don’t know
why it fails when writing to the db - my schema matches the 3.8.1
schema file.
Chris
I can try that … did you know if that changed in 3.8.0 to 3.8.1?
Do you know what the database schema upgrade in the UPGRADING.mysql is
for? I haven’t gotten through that step without errors, but 3.8.0. seems
to work just fine without successfully getting through it.
Thanks for the suggestions
TrentFrom: Chris Nelson [mailto:cnelson@delivra.com]
Sent: Thursday, September 11, 2008 10:46 AM
To: Golemon, Buck
Cc: Trenton Taylor; rt-users@bestpractical.com
Subject: Re: [rt-users] RT 3.8.1: “Tickets” interface logs you out
I may be way off here (I’m a total newbie). But Todd Green wrote this a
couple days ago - might this help?
Just hit and fixed this issue yesterday. My solution was to was to
add
the following to
etc/RT_SiteConfig.pmSet($WebSessionClass , ‘Apache::Session::File’);
When I asked him what it was actually doing, this is what he said:
In my digging I determined that by default the sessions are being
written to the SQL database. Notes from others having similar issues
indicated this might be part of the issue. My current production
environment (3.4.2) writes the sessions to files instead of to the
database so I used the same option in the new environment as well.
Sorry if that’s not helpful.
-Chris
Chris,
I think I saw something here about setting the DB session table (MySQL)
to not nulls or some default like that. Check the thread in the users
list and you’ll find it. Hope this helps.
Kenn
LBNLOn 9/11/2008 10:52 AM, Chris Searle wrote:
On 11. sep… 2008, at 19.46, Chris Nelson wrote:
I may be way off here (I’m a total newbie). But Todd Green wrote
this a couple days ago - might this help?Just hit and fixed this issue yesterday. My solution was to was
to add
the following to
etc/RT_SiteConfig.pmSet($WebSessionClass , ‘Apache::Session::File’);
I have to say that this worked for me as well. Although I don’t know
why it fails when writing to the db - my schema matches the 3.8.1
schema file.
I think I saw something here about setting the DB session table
(MySQL) to not nulls or some default like that. Check the thread in
the users list and you’ll find it. Hope this helps.
Didn’t find that. Summary of what I found:
So far the only working fix for me is using Apache::Session::File.
If I throw the old 3.8.0 install and db back up the issue goes away.
Chris
|#
|# Didn’t find that. Summary of what I found:
|#
|# 3) a_session should be longblob not longtext (not sure where this
|# comes from - the etc/schema.mysql of 3.8.1 shows longtext - which I
|# have kept since it matches the schema file).
Changing to longblob fixed mine quite a few versions back when
I was having this re-login problem after one upgrade…
Field Type Collation Attributes Null Default
a_session longblob BINARY Yes NULL
Tim Rosmus <trosmus@nwnexus.net>
Postmaster / USENET / DNS
Northwest Nexus Inc. / NetOS Inc.|# 3) a_session should be longblob not longtext (not sure where this
|# comes from - the etc/schema.mysql of 3.8.1 shows longtext - which I
|# have kept since it matches the schema file).Changing to longblob fixed mine quite a few versions back when
I was having this re-login problem after one upgrade…Field Type Collation Attributes Null Default
a_session longblob BINARY Yes NULL
OK. Since I’d tried everything else - I gave it a go.
It does appear to work.
Now this I found interesting:
/opt/rt3/etc/schema.mysql
CREATE TABLE sessions (
id char(32) NOT NULL,
a_session LONGTEXT,
LastUpdated TIMESTAMP,
PRIMARY KEY (id)
);
/opt/rt3/etc/schema.mysql-4.1
CREATE TABLE sessions (
id char(32) NOT NULL,
a_session LONGBLOB,
LastUpdated TIMESTAMP,
PRIMARY KEY (id)
);
I’m running mysql 5.0.32. So - why the 4.1 schema is fine but the
other one isn’t I don’t know 
Is it an error in the non 4.1 schema
or ??
Anyhow - I’ll leave it at longblob and see how it goes.
Chris
After some work, I determined that a blank database worked fine, and
looking at the UPGRADING.mysql file, I fixed the problem with these
commands (as documented therein):
cd ~/packages/rt-3.8.1/
perl etc/upgrade/schema.mysql-4.0-4.1.pl rt3 root ‘some_password’ >
sql.queries
(you have to edit the file and replace any “BLOB CHARACTER SET blah”
with just BLOB)
cat sql.queries | mysql -D rt3
–Buck-----Original Message-----
From: rt-users-bounces@lists.bestpractical.com
[mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of Golemon,
Buck
Sent: Thursday, September 11, 2008 10:30 AM
To: Trenton Taylor; rt-users@bestpractical.com
Subject: Re: [rt-users] RT 3.8.1: “Tickets” interface logs you
out
So you think it's in regard to upgrading?
I'll try with a fresh database and let you know how it goes.
--Buck
-----Original Message-----
From: Trenton Taylor [mailto:trentt@ssi-invest.com]
Sent: Thursday, September 11, 2008 10:26 AM
To: Golemon, Buck
Subject: RE: [rt-users] RT 3.8.1: "Tickets" interface
logs you out
A bunch of us have the issue but it's being ignored on
the lists …
I think jesse considers it our problem for not upgrading
correctly.
I upgraded from rt 3.6.6 to 3.8.0 and ran the upgrade
script at the end of the install … no errors and no “log out” issues
in the interface
I then upgraded from 3.8.0 to 3.8.1 and ran the upgrade
script that was mentioned at the end of the install … no errors but am
logged out on some web clicks.
I went back to 3.8.0 and don't have any problems now ...
Did you follow the UPGRADING.mysql document? I got
errors when trying it.
Nobody has responded to me on the list ..
From: rt-users-bounces@lists.bestpractical.com
[mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of Golemon,
Buck
Sent: Thursday, September 11, 2008 9:17 AM
To: rt-users@bestpractical.com
Subject: [rt-users] RT 3.8.1: “Tickets” interface logs
you out
After installing a new version of RT, I've noticed that
whenever I click “Tickets” or interact with the query builder such that
it reloads the page, it logs me out. I still remembers it’s state after
I log back in, but this is extremely annoying.
Has anyone else had this problem?
Please let me know if there's any other information you
need.
--Buck
Important: The information contained in this e-mail
message is confidential and is intended only for the named addressee(s).
If the reader of this e-mail message is not an intended recipient (or
the individual responsible for the delivery of this e-mail message to an
intended recipient), please be advised that any re-use, dissemination,
distribution or copying of this e-mail message is prohibited. If you
have received this e-mail message in error, please reply to the sender
that you have received the message in error and then delete it. Thank
you.
No virus found in this incoming message.
Checked by AVG - http://www.avg.com
Version: 8.0.169 / Virus Database: 270.6.19/1664 -
Release Date: 2008-09-10 7:00 PM
I’m running mysql 5.0.32. So - why the 4.1 schema is fine but the
other one isn’t I don’t know
or ??
It seems that naming of that upgrade file is somewhat misleading based
on the problems people are having because they did not follow those
instructions (I did not have Mysql 4, I have 4.1, 5, etc. already)
You need to follow the instructions if you are upgrading from < 3.8 to
3.8.1 no matter what your mysql database version is. That’s my
understanding.
You need to follow the instructions if you are upgrading from < 3.8 to
3.8.1 no matter what your mysql database version is. That’s my
understanding.
Ah. My understanding of the UPGRADING.mysql doc was that you needed to
run it for converting from mysql 4.0 to 4.1. Since my 3.6.x install
was running fine on MySQL 5.x I simply assumed that this was already
in place. And my assumption of the naming of the schema files
was .mysql for current (5.x) and .mysql-4.1 for older (4.x). It seems
that its .mysql for old, .mysql-4.1 for 4.1 and later.
I’d also assumed that the make upgrade process that runs a schema
update for you after prompting you for the version you were running
before included this change. That would be my bad assumption.
Odd - now reading back through both documents I can’t actually see how
I came to that conclusion - but there you go.
Now my only issue is getting a late enough copy of dbd::mysql on the
box where only 3.008 is in the package tree - without breaking
everything else that uses it
Chris