24too many open files apache

Since there's many answers to this question "Too many open files 24 " and how to solve it just increasing number of allowed open files limit i have not found any suggestion how to check who is using these files. Is there any tool to check who's using these files since my virtual box machine actually is sleeping by htop?

These files contain the session data of your visitors. A long-term solution would be to expire your sessions more often. In this question you can find, how can you set up in your php to automatically remove expired session files. On my opinion, setting session.

If you have only a small site with a few visitors at most some tens daily , it is far enough if you delete the old session files daily from crontab. If you have a big site, or you want a super user-friendly but not so secure site, you need to be able to handle a lot of sessions. On my opinion, in this case it is better if you use some alternate php session solution with a database backend.

The following works on a high-load CentOS 7 system and should work on your CentOS 8 system too but before you apply these settings please understand that doing so can and will, on very high loads make the system unstable. Let us know if this has increased the open file limit on your system and the error has disappeared.

This applies to a centos8 system where under systemd there are system wide file descriptor limits and per-process file descriptor limits When apache starts its as the root user, then when its grabbed the ports it switches to run under the httpd user And this is where my confusion arose and the suggestion by calport didnt work. Possible duplicate of stackoverflow. Add a comment. Active Oldest Votes. Sign up or log in Sign up using Google. Sign up using Facebook.

Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Stack Gives Back Thanks, though. Nope, we've got a dedicated virtual server dv - our resources are solely limited to our own virtual environment.

No, we have not had any major increase in traffic, nor have we added any new features. Sounds like you've got the immediate problem figured out, but I would recommend thinking further about why you hit the limit -- you ought to be able to predict when it'll happen again by keeping an eye on your open file descriptors vs. Okay, I think the more appropriate term is "worked around". I've noticed that we're still running into some intermittent issues relating to some tuning of MySQL.

My theory is that some small tuning of MySQL caused more on-disk files to be put into use, which cascaded down into Apache issues. Don't quote me on this. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Stack Gives Back Safety in numbers: crowdsourcing data on nefarious IP addresses. Featured on Meta.

New post summary designs on greatest hits now, everywhere else eventually.