Hello, We are using Pylons 1.0 with Beaker 1.5.4 for sessions. Many users of our site have experienced unexpected logouts, like their sessions are suddenly invalidated or expired. We're using file-backed beaker sessions (only running on one machine right now). Sessions are configured with the usual config:
cache_dir = %(here)s/data beaker.session.key = ourkey beaker.session.secret = oursecret So we are not changing timeouts from the default or anything like that. The session cookie in the browser is properly set to expire when the browser closes. However, users are seemingly randomly being logged out. It doesn't seem to matter what URL or action they are hitting. It's hard to reproduce, but it does happen reliably several times a day for users. Oh, and in all kinds of browsers. I've combed through our code to make sure we aren't doing anything stupid with the session, like deleting it (or deleting the 'user_id' item) inadvertently. In fact, the only place we delete the session is in the logout action. I've also looked through the Beaker code, and nothing jumps out at me. The only thing I can think of is a possible interaction between how Beaker's FileNamespaceManager does file locking and the disk of the VPS we're deployed on. It's ext3 on a network attached storage device. Anyway, I'm just hoping someone out there might have a hint about what might be going on here. I think my next step is to just swap in a different session store, like a database. But I'd like to have a grasp on what is going on here first. Greg -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
