Am 15.02.2011 13:08, schrieb jo: > This is very strange, Christoph, because the procedure runs in about > a dozen installations and in all of them, there is this same error. > Is it possible that all installations have the session file corrupted
Then has it worked in the past and you're seeing these errors only now? Maybe all of the installations are saved on the same harddisk partition that is corrupt or full or reached a quota or there is some kind of hot backup/restore or sync mechanism active on the session directories? Or maybe you started to store some strange things in the session which cause the unplicking to fail? Do the installations use different directories for storing the sessions? Do you set session_filter.storage_path in the config? Btw, if you can't get file based sessions to work, maybe RAM sessions are an option for you (set session_filter.storage_type=Ram)? And CherryPy also allows a PostgreSQL database as backend. Another option are visit based sessions, but I have gested and documented that only with TG 1.5: http://docs.turbogears.org/1.5/VisitBasedSessions -- Christoph -- You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en.
