Continual re-login issue -revisted on 3.6.4

Hi there;
Just upgraded my dev system to 3.6.4 from 3.6.1 few other perl modules
were upgraded,
dbix to 1.49
DBD-MySQL.i386 3.0008
Text::Quoted version 2.02
Module::Versions::Report version 1.03

Removed all local customisation so the only thing that is not of the box
is RT_SiteConfig and the database , restarted apache and now with every
click I get the login page.
I had the same problem when first upgraded to 3.6.1 and was eventually
fixed by using dbd-3.0006 and the following sql statement:
ALTER TABLE sessions CHANGE a_session a_session LONGBLOB;

However these don’t seem to work now … Anybody else got this problem …
or ist just my stupid system?? ideas?
The db is on a separate host from web and I use ssl (in case it
matters), the os is centOS 4, and mysql version 5
Roy

Roy El-Hames wrote:

Hi there;
However these don’t seem to work now … Anybody else got this
problem …
or ist just my stupid system?? ideas?
The db is on a separate host from web and I use ssl (in case it
matters), the os is centOS 4, and mysql version 5
Roy

No, I’m on rt-3.6.4, upgraded from 3.6.3, and I need to login twice,
most of the time. I use file based sessions and will try it on a
absolutely clean install as soon as I have time to do so. I’m currently
upgrading my RT instance.
But I can tell you that it hasn’t gone away completely with 3.6.4 as the
release notes state.

Joop

Thanks Joop for mentioning the “release notes”, reading the Changelog

M /rt/branches/3.6-RELEASE/html/Elements/SetupSessionCookie

  • calc id of a session in $SessionCookie var
  • add $session_properties variable
    ** use it in both attempts to tie
    this should fix potential relogin problems

By copying SetupSessionCookie of version 3.6.1 to local/html/Elements/
in 3.6.4 seems to have fixed the issue for me.

Regards;
Roy

Joop wrote:

Roy,

We're getting it also. It seems to be related to executing a 

function/selection the first time in a session. Once I have selected,
let’s say Query, it goes to the signon page, but every time I select
that afterwards, it’s fine. Must be related to cookies or cache or
something like that.

Kenn
LBNL

Roy El-Hames wrote: