-
-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
inode filling up #173
Comments
The hosting provider has installed a clean-up script which will run nightly. To see where it's located: sudo crontab -l The contents of the script: #!/bin/sh
find [path]/[to]/lmms.io/tmp -maxdepth 1 -type f -name 'sess*' -mtime +12 -exec rm -f {} \; They said this is caused by us not using the standard |
👍 |
This is still occurring. Reopening. |
Support says:
We'll see how well that works. Closing back out for now. |
This is still happening. |
Re-notified support. We'll see what happens. |
What part of the code is putting items in the tmp directory? Is it a rudimentary cache? |
No issues in 1 year. Closing. |
This happened again today, the forums are down, cleaning the tmp dirs rn |
Support is claiming it's happening due to the |
Ok... I found something...
Just cd'ing to the directory takes almost 60 seconds. I'm not sure what created this or what its contents are. I'm still investigating. |
Ok... Of the 1,301,401 files, 1,300,215 of them are named ~/lsp_data/11880 $ find . -name . -o -prune | head
.
./sess_thuucbafmnui84mdi6s11qbus0
./sess_ti11pl4hba7fe0jv2tku2n3l57
./sess_ti5cgc2vlps37rh967dghru6k1
./sess_ti7d4pq92ofhr9bm1fmvugl0q4
./sess_ti9c7e3pvhicqd66j8u3edt5a2
./sess_ti9gq8bk8r4tpvriid13ou7i27
./sess_ticg8blksfrtqs7kbchis1m2e4
./sess_ticgf7fknuhkbovsj7lsuknnj5
./sess_ticv4b8aacohckr7bu8797q2i5 I'm not sure what else is inside this folder, but we can purge these sessions for now and then debug why they're getting misplaced. |
This happened again today, but it affected the download page #295 I don't know what happened to the Current status of the inodes:
All of them were used before my cleaning. |
The issue was I migrate the website to Symfony so that the temporary folder path changed.
I have modified the clean up script located at |
#281 mentions that
Just something to keep an eye out for :P |
We've migrated to new hosting, this issue hasn't happened, so I think we're good. |
Many items of our site go down when our own
./tmp
directory fills up (1 million+ entries). Most notably, the forums.Since this is the second time this has occurred, I'm documenting the steps we used last time, so we have a work-around until a permanent solution is determined.
... and optionally, if some services are still acting up, bounce the Fast CGI processor...
In the mean time, I've opened a ticket with our hosting provider (NetworkRedux) to see what's the preferred method for cleaning this up.
The text was updated successfully, but these errors were encountered: