We recently completed an upgrade of RT from version 3.3 to 3.8.7, we also
moved it out of the building to a server located in our data centre.
Now there’s a problem which occurs at random times through the day but
mostly in the morning. Sometimes you’ll go to RT and find yourself logged
out and sometimes you’ll find yourself logged in as someone else (the
worrying thing is that sometimes it takes a while to notice you’re using
someone elses account)
Now in years of using the old version this never happened, now it’s
happening several times a day. I think the key thing is now that the server
is in the data centre so as far as RT is concerned we are all coming from
the same IP
So my question is , does RT cache IPs and if so, how can we disable this?
We recently completed an upgrade of RT from version 3.3 to 3.8.7, we also
moved it out of the building to a server located in our data centre.
Now there’s a problem which occurs at random times through the day but
mostly in the morning. Sometimes you’ll go to RT and find yourself logged
out and sometimes you’ll find yourself logged in as someone else (the
worrying thing is that sometimes it takes a while to notice you’re using
someone elses account)
Now in years of using the old version this never happened, now it’s
happening several times a day. I think the key thing is now that the server
is in the data centre so as far as RT is concerned we are all coming from
the same IP
So my question is , does RT cache IPs and if so, how can we disable this?
RT doesn’t cache IPs, doesn’t use IP based auth and shouldn’t behave
like you describe. Do you have proxy between data center and you?
Where do you store user’s sessions: on disk or in DB?
There’s no proxy and this location has unlimited access through the firewall.
regarding the sessions, I’m not 100% sure but there is a table in the RTDB
called “sessions” and that’s actively being updated. Also, the database is
on the same server as RT
So my question is , does RT cache IPs and if so, how can we disable this?
RT doesn’t cache IPs, doesn’t use IP based auth and shouldn’t behave
like you describe. Do you have proxy between data center and you?
Where do you store user’s sessions: on disk or in DB?
We recently completed an upgrade of RT from version 3.3 to 3.8.7, we also
moved it out of the building to a server located in our data centre.
Now there’s a problem which occurs at random times through the day but
mostly in the morning. Sometimes you’ll go to RT and find yourself logged
out and sometimes you’ll find yourself logged in as someone else (the
worrying thing is that sometimes it takes a while to notice you’re using
someone elses account)
Now in years of using the old version this never happened, now it’s
happening several times a day. I think the key thing is now that the server
is in the data centre so as far as RT is concerned we are all coming from
the same IP
So my question is , does RT cache IPs and if so, how can we disable this?
That’s not RT caching IPs. It’s very common that a number of users all hit RT from the same IP. That sure sounds like there’s now a badly behaved caching proxy between RT and your users. Maybe it’s a squid someone set up to “make things faster”?
There is a proxy in the building but we bypass that ourselves. We did have
squid on the server that RT used to be on but we haven’t used that in years
So my question is , does RT cache IPs and if so, how can we disable this?
That’s not RT caching IPs. It’s very common that a number of users all hit
RT from the same IP. That sure sounds like there’s now a badly behaved
caching proxy between RT and your users. Maybe it’s a squid someone set up
to “make things faster”?
There is a proxy in the building but we bypass that ourselves. We did have
squid on the server that RT used to be on but we haven’t used that in years
I’d put (small amounts of) money on there being some sort of a proxy (or possibly an apache reverse-proxy configuration) which is serving out cached versions of pages with users’ cookies.
I’ve asked about and there is no proxy server, there’s a content filtering
appliance but we don’t go through that at all, that’s another department.
Jesse Vincent wrote:
There is a proxy in the building but we bypass that ourselves. We did
have
squid on the server that RT used to be on but we haven’t used that in
years
I’d put (small amounts of) money on there being some sort of a proxy (or
possibly an apache reverse-proxy configuration) which is serving out
cached versions of pages with users’ cookies.
I’ve asked about and there is no proxy server, there’s a content filtering
appliance but we don’t go through that at all, that’s another department.
Jesse Vincent wrote:
There is a proxy in the building but we bypass that ourselves. We did
have
squid on the server that RT used to be on but we haven’t used that in
years
I’d put (small amounts of) money on there being some sort of a proxy (or
possibly an apache reverse-proxy configuration) which is serving out
cached versions of pages with users’ cookies.
I recall this coming up on the mailing list a few months ago - it was an
apache module, although the name escapes me at the moment. You’d have
to search the archives.