On Jul 29, 2006, at 8:43 PM, Brian Shih wrote:

> In our beta-testing, anytime we deploy a new version of the app
> (install the egg, kill existing paster, start new paster, restart
> lighttpd) it loses all session info and logs everyone out. This is a
> problem for people editing things in the middle of an upgrade.
>
> Does anyone know of a way to preserve sessions between upgrades?
>
> I tried making a symlink at app/cache/sessions to point to a static
> /var/local/app/sessions folder, but it still seems to kick everyone  
> out
> on an upgrade.
>
> Does anyone know what the other folders in cache do? (obj and lock)

What does your config ini look like? Assuming you're using Pylons  
0.9, the Beaker middeware isn't changing, and isn't likely to change  
anytime soon so upgrading shouldn't be a problem. The most reasonable  
explanation, that you could test by logging in then restarting  
paster, is to see if the sessions for some reason are using memory  
instead of disk files.

HTH,
Ben

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to