<p>It sounds like your sessions are not being sticky. How many servers? </p>

<p>Are you having to login multiple times as well to get things done?</p>

<p>Apart from what Brad mentioned, couple things I'd try if you haven't already:</p>

<ul>
<li>Set an <a href="http://buildwithcraft.com/docs/config-settings#appId" rel="nofollow noreferrer"><code>appId</code></a> in the config settings. You didn't mention AWS but setting an appId seems to have <a href="https://craftcms.stackexchange.com/questions/9617/sessions-being-read-inconsistently/9723#9723">solved it</a> for at least one other poster using multiple servers.</li>
<li>Set <a href="http://buildwithcraft.com/docs/config-settings#overridePhpSessionLocation" rel="nofollow noreferrer"><code>overridePhpSessionLocation</code></a> and feed it your redis server (or auto). (It's possible Craft isn't even using Redis if it's not getting set correctly.)</li>
</ul>

CC BY-SA 3.0
2015-06-10T18:58:42.533Z
Worth mentioning that if `overridePhpSessionLocation` is set to `auto`, then Craft is specifically looking for the string `tcp://` in the session save path to determine if it's on some memory based caching environment like Reddis or Memcache.
Brad Bell
CC BY-SA 3.0
2015-06-10T20:50:07.080Z
I think we resolved the issue. It turned out to be something related to the cache lifetimes.
Jay El-Kaake
CC BY-SA 3.0
2015-06-10T18:55:56.883Z
2015-06-10T18:55:56.883Z
2017-04-13T12:50:59.930Z
RitterKnight
<p>It sounds like the PHP session file isn't being removed from Reddis when you click logout the first time.</p>

<p>The first thing I'd do is, after clicking logout one time, query Reddis to see if that file still exists in memory.  If it does, there is probably some other configuration issue causing it from being deleted.</p>

CC BY-SA 3.0
2015-06-10T20:51:32.217Z
Yeah unfortunately I didn't have access to our reddis server, but the problem was solved by fixing the cache lifetimes. The techops part of our organization handled it and unfortunately didn't report the exact fix :(
Jay El-Kaake
CC BY-SA 3.0
2015-06-10T18:52:35.193Z
2015-06-10T18:52:35.193Z
Brad Bell
<p>We're using Craft CMS (pro) across multiple application servers and using reddis to manage the sessions.</p>

<p>We're needing to click on 'log-out' twice, sometimes several times before it actually logs us out of the control panel.</p>

<p>Any idea what could be causing this?</p>

<craft-pro>
Mutliple logouts required on Multiple App Servers
# Mutliple logouts required on Multiple App Servers

(Asked by: username_0 on 2015-06-10)

We're using Craft CMS (pro) across multiple application servers and using reddis to manage the sessions.

We're needing to click on 'log-out' twice, sometimes several times before it actually logs us out of the control panel.

Any idea what could be causing this?

**Tags:** craft-pro

---

## 2 answers

### Answer by username_1 on 2015-06-10. Score: 3 | Accepted answer

It sounds like your sessions are not being sticky. How many servers?

Are you having to login multiple times as well to get things done?

Apart from what Brad mentioned, couple things I'd try if you haven't already:

* Set an [`appId`](http://buildwithcraft.com/docs/config-settings#appId) in the config settings. You didn't mention AWS but setting an appId seems to have [solved it](https://craftcms.stackexchange.com/questions/9617/sessions-being-read-inconsistently/9723#9723) for at least one other poster using multiple servers.
* Set [`overridePhpSessionLocation`](http://buildwithcraft.com/docs/config-settings#overridePhpSessionLocation) and feed it your redis server (or auto). (It's possible Craft isn't even using Redis if it's not getting set correctly.)

> **Comments:**
> **username_2**: Worth mentioning that if `overridePhpSessionLocation` is set to `auto`, then Craft is specifically looking for the string `tcp://` in the session save path to determine if it's on some memory based caching environment like Reddis or Memcache.  
> **username_0**: I think we resolved the issue. It turned out to be something related to the cache lifetimes.  

---

### Answer by username_2 on 2015-06-10. Score: 0

It sounds like the PHP session file isn't being removed from Reddis when you click logout the first time.

The first thing I'd do is, after clicking logout one time, query Reddis to see if that file still exists in memory. If it does, there is probably some other configuration issue causing it from being deleted.

> **Comments:**
> **username_0**: Yeah unfortunately I didn't have access to our reddis server, but the problem was solved by fixing the cache lifetimes. The techops part of our organization handled it and unfortunately didn't report the exact fix :(  

---

