RT develops sudden bouts of amnesia regarding logged-in users

First off, let me apologize for running a fairly ancient version of RT. We
are on 2.0.11pre, which is equivalent to 2.0.12.

Quite some time ago I hacked our system to authenticate against our Novell
NDS via LDAP. This has worked happily for a few years now.

Today RT has begun kicking people out a lot. After you log in, you might
get to view a ticket or do a search, but if you try to refine your search or
click a header to sort a different way, or tweak the people attached to a
ticket, just for instance, you often find yourself staring at the login
screen again. Logging in again generally gets you where you were trying to
go (although search criteria are often forgotten). But you’ll probably have
to re-re-login again several clicks later.

Occasionally, a page will appear to have worked fine, but on closer
inspection, it’s missing something. For instance, a ticket displays pretty
much fine, but the contents of all the correspondence is not shown. Or a
combo box of potential ticket owners has no contents.

My very-slightly-educated guess is that our LDAP server might be flipping
its lid and bouncing people, sometimes right in the middle of a page render,
which could explain the partly rendered pages.

Or am I barking up the wrong tree? Does this sound more like something else
that anyone can recognize?
Kendric Beachey

This e-mail and any attachments may contain confidential material for the sole use of the intended recipient. If you are not the intended recipient, please be aware that any disclosure, copying, distribution or use of this e-mail or any attachment is prohibited. If you have received this e-mail in error, please contact the sender and delete all copies.
Thank you for your cooperation

Beachey, Kendric wrote:

First off, let me apologize for running a fairly ancient version of RT. We
are on 2.0.11pre, which is equivalent to 2.0.12.

Quite some time ago I hacked our system to authenticate against our Novell
NDS via LDAP. This has worked happily for a few years now.

Today RT has begun kicking people out a lot. After you log in, you might
get to view a ticket or do a search, but if you try to refine your search or
click a header to sort a different way, or tweak the people attached to a
ticket, just for instance, you often find yourself staring at the login
screen again. Logging in again generally gets you where you were trying to
go (although search criteria are often forgotten). But you’ll probably have
to re-re-login again several clicks later.

Occasionally, a page will appear to have worked fine, but on closer
inspection, it’s missing something. For instance, a ticket displays pretty
much fine, but the contents of all the correspondence is not shown. Or a
combo box of potential ticket owners has no contents.

My very-slightly-educated guess is that our LDAP server might be flipping
its lid and bouncing people, sometimes right in the middle of a page render,
which could explain the partly rendered pages.
LDAP could bounce user only when you request for auth, RT request auth
only once when you enter login, then once per request to revalidate I think.

I can’t comment on other things I don’t know how RT2.x works, but anyway
logs could help(apache, rt…)