Tickets :: [#8792] horde_sessionhandler table grows bigger and bigger

6.0.0-beta6

4/9/26

Summary	horde_sessionhandler table grows bigger and bigger
Queue	Horde Base
Queue Version	3.3.6
Type	Bug
State	Not A Bug
Priority	2. Medium
Owners
Requester	michael (at) bigmichi1 (dot) de
Created	12/20/09 (5954 days ago)
Due
Updated	12/21/09 (5953 days ago)
Assigned	12/21/09 (5953 days ago)
Resolved	12/21/09 (5953 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

12/21/2009 07:55:59 PM	Michael Slusarz	Comment #6 State ⇒ Not A Bug	Reply to this comment
I've added some test checks in Horde 4.

12/21/2009 07:55:37 PM	CVS Commit	Comment #5	Reply to this comment
Changes have been made in CVS for this ticket: ~~Bug: 8792~~ check for session gc values http://cvs.horde.org/diff.php/horde/test.php?rt=horde&r1=1.193&r2=1.194&ty=u

12/21/2009 07:30:10 PM	michael (at) bigmichi1 (dot) de	Comment #4	Reply to this comment
ok the problem is now solved, thank you for pointing in the right direction with these php.ini settings, but still it would be nice to have these checked in test.php from horde

12/21/2009 07:13:37 PM	michael (at) bigmichi1 (dot) de	Comment #3	Reply to this comment
ok i think i found the solution, will now test it. on debian the setting for "session.gc_probability = 0", can there be some sort of check in the test.php, that looks for that configuration values?

12/21/2009 06:37:48 PM	Michael Slusarz	Comment #2 State ⇒ Feedback	Reply to this comment
If garbage collection is not being called, it is an issue with PHP. See: http://www.php.net/manual/en/session.configuration.php#ini.session.gc-divisor http://www.php.net/manual/en/session.configuration.php#ini.session.gc-maxlifetime http://www.php.net/manual/en/session.configuration.php#ini.session.gc-probability

12/20/2009 10:52:48 AM	michael (at) bigmichi1 (dot) de	Comment #1 Priority ⇒ 2. Medium Type ⇒ Bug Summary ⇒ horde_sessionhandler table grows bigger and bigger Queue ⇒ Horde Base Milestone ⇒ Patch ⇒ No State ⇒ Unconfirmed	Reply to this comment
my horde_sessionhandler table gets bigger and bigger (driver: mysql based sessions). i think there should be some sort of garbage collector running on the table. the code in mysql.php has a gc function but i can't find a call to this function in the entire code. my horde_sessionhandler table has now 10267 entries. and when running the sql 'select * from horde_sessionhandler where `session_lastmodified` < 1261306002' with 1261306002 is time() - 300 i got 10265 entries listed with the oldest timestamp is 1257691733. and this is really old.