[horde] Memcached sessions don't expire after upgrade to 5.1.0

[Michael M Slusarz]

Quoting Ralf Lang <lang at b1-systems.de>:

> On 27.06.2013 05:35, OVi C wrote:
>> Hi.
>> After upgrading to latest horde groupware webmail version 5.1.0 from 5.0.5,
>> there seems to be a lot of sessions opened from the last days.  Also using
>> the command line horde-active-session it shows that there are active
>> sessions, but there is nobody logged in. Even when I close the browser the
>> session aren't killed. I'm using memcached to store the session
>> information.  Prior to upgrade the sessions would expire gracefully, now it
>> seems to add up every time users log in.
>> They only go away if I restart the memcached service.
>>
>> Any hints ?
>>
> As described some days ago, it is advised NOT to use memcached for
> sessions in 5.1 and to use redis instead of memcached if possible.

This is more likely a reporting issue that may have been fixed in  
Horde_Core (check github for commits).  More important: nobody has  
demonstrated that these sessions *actually* exist (session counting !=  
sessions existing).

But what Ralf said.  Don't use memcache as a sessionhandler.

michael

___________________________________
Michael Slusarz [slusarz at horde.org]