|
sheathe
|
March 19, 2021 at 3:24 pm
Hi,
Any idea why Event Espresso 3.1.37.14 is creating thousands of PHP session files in /var/tmp on our server and they are not being removed for some reason?
We only discovered this because backups were timing out – even after deleting all the session files more than two weeks old, there are still total 545788 files in that folder.
I’m going to upgrade to the most recent version of EE3 asap, but I don’t see any mention of this in the change log.
Sample Filename:
sess_vvvv0vbkk6lp1qr8r161hc2mk5
Sample contents of file:
espresso_session|a:3:{s:2:”id”;s:50:”vtlpb4tr9s4i9cvv3evo8c8san-6044a9e0c074b5.25403138″;s:17:”events_in_session”;a:0:{}s:11:”grand_total”;s:0:””;}
Thank you for any help.
|
|
sheathe
|
March 22, 2021 at 4:55 pm
This reply has been marked as private.
|
|
sheathe
|
March 22, 2021 at 4:58 pm
This reply has been marked as private.
|
|
Tony
|
March 23, 2021 at 8:26 am
Hi there,
Event Espresso 3 just runs session_start() to start (and use) a session, it does not clear sessions and leaves that to your server, if you check your phpinfo() output does you have a value set for session.gc_maxlifetime?
I don’t think upgrading to the latest version will change this, although I still do recommend you do.
We only discovered this because backups were timing out – even after deleting all the session files more than two weeks old, there are still total 545788 files in that folder.
The default lifetime of sessions is 24mins, do you need to keep 2 weeks worth of sessions?
Is this a high traffic site?
Is there a way to know specifically which files have changed in each version?
The only other way can think of to review the git repo HERE
If using DiffMerge there is an option to skip EOL validation:
https://sourcegear.com/diffmerge/webhelp/sec__rule__dialog__line__term.html
|
|
sheathe
|
March 23, 2021 at 9:42 am
Thank you for your response – will look into this with our hosting provider.
Thanks for the link to the git repo too.
|
