• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue AH01071 Failed to open stream: Too many open files in ...

JohnWest

New Pleskian
Server operating system version
Ubuntu 22.04.5 LTS
Plesk version and microupdate number
lesk Obsidian v18.0.64_build1800241008.13 os_Ubuntu 22.04
Hi All,

I've got a server with 3 domains on it.
Nothing too crazy here.

One of the website is recently experience error 500.
It seems to be that the site grew recently and I'm hitting an error I've not encountered before.

AH01071: Got error 'PHP message: Failed to open stream: Too many open files in ….
follow by bunch of files that errored out when a page load.

I'm not an expert so I checked online here and there, but it wasn't clear if the issue would be something I can fix with a per domain setting (some suggest NGINX level instruction), or Apache (domain level instructions), or apache module overall, or event the whole system.

What's certain is that when this error hits, only this domain is experiencing issues. Not the others on the same server. Which would point me towards a resolution that can be implemented with domain level settings.

Looking forward to hear about suggestions.
 
Back
Top