Revo 2.1.1 logs me out every 2 minutes...

Does anybody have an idea why the manager of Revo (after updating to 2.1.1) logs me out every 2 minutes or hangs up on saving a resource?

Is there anything what we maybe did wrong in the updating-process?

Any idea? I use Chrome as well as Firefox...

Letti

Try setting the value of the new System Setting session_gc_maxlifetime to a value of 640800 or similar (this is 7 days) and see if that prevents the issue you are experiencing. Also, what is the session.gc_maxlifetime value in your PHP ini settings?

Thanks a lot, this helped. The value in our PHP ini settings was 1440. Shouldn´t this normally prevent an automatically logout for 24 minutes? In our settings the log outs appeared already after a few minutes...

Do you know why this problem just appeared after upgrading to revo 2.1.1 and not in revo 2.1.0?

Letti

Well, some improvements in session handling were made, especially when caching session records, but I just realized if you don’t have a value set in System Settings for session_cookie_lifetime, it may be setting the gc_maxlifetime to 0 inappropriately. What is your session_cookie_lifetime value in System Settings? It really depends on the gc_divisor and gc_probability settings on your server, as well, but remember, any PHP script that executes on your server will trigger the garbage collection process based on the settings it is using. This effectively applies the values from the script with the most aggressive gc settings to all PHP sessions on that machine.

Quote from: OpenGeek at Jun 15, 2011, 08:06 AM

Well, some improvements in session handling were made

Will the "session_gc_maxlifetime"-fix be part of 2.1.2? New users would like to have that with their fresh installation. ;-)

Quote from: mindeffects at Jun 22, 2011, 09:34 AM

Quote from: OpenGeek at Jun 15, 2011, 08:06 AM

Well, some improvements in session handling were made

Will the "session_gc_maxlifetime"-fix be part of 2.1.2? New users would like to have that with their fresh installation. ;-)

TBH, I’m not sure there is a bug/fix clearly identified here—I’ve been testing the session handling in-depth and have not encountered an issue with or without a value set in the session_gc_maxlifetime System Setting. That said, some other changes related to sessions have been made in preparation for 2.1.2 release that may have resolved whatever specifically was causing the OP’s 2-minute logouts. In particular, it could have been related to bug #5001, but again, I’m not certain.