Hi, I noticed that my server used 40GB more space than it should have. And after a long investigation i found out that the "tmp" folder was full of 0KB's sess_* files. I couldn't even open the folder because of the amount of files in it. So i had to run an extra command for over a day to empty this "tmp" folder. But it's not over yet this "tmp" folder still gets spamed with 1000's of sess_* files per hour. Dose someone know why this happens? I didn't had this problem with php5.6 and my website even uses the MySQL Database to save the sessions of the site visitors.
Fixed in 3.2 and above. See https://www.howtoforge.com/communit...es-are-not-cleaned-up-in-ispconfig-3-2.85938/ aswell.
Is it possible to get the php5.6 behavior back. I never saw my "tmp" folder getting spamed with sess_* files with php5.6. I feel a little bit uncomfortable to have something spamming my "tmp" folders with useless files, and blocking me from even opening it because of the amount of files that are being saved in this "tmp" folders in less than an hour with a medium traffic website.
I am not sure but I thought Debian and Ubuntu cleaned them up automatically for PHP 5. So no different behaviour there. And some PHP applications clean them up themself.
Don't know how Debian 9 cleaned them up before, but i never saw those sess_* files in the "tmp" folder before with php5.6. It would be interesting to know how big websites are dealing with this sess_* file spam problem.
Some other webpages on this: https://stackoverflow.com/questions/654310/cleanup-php-session-files https://magento.stackexchange.com/q...handle-session-files-that-become-too-numerous
I think the sess* files not getting teleted is a bug that appeard in the beginning of november 2019. It is fixed in ISPConfig 3.2 like @Th0m wrote and I assume the fix can be backported to ISPConfig 3.1.15. Meanwhile, I have a script that removes those old sess_files, and it works very fast so does not take a day to remove some ten million files. https://www.howtoforge.com/communit...l-tmp-sessions-not-deleted.41752/#post-402190
Even if the "tmp" folder is now getting cleaned up. We still can't open it be because of the amount of new "sess_*" files that are getting spammed into that folder.
