• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

mmap cache can't open - Too many open files

P

PixyPumpkin

Guest
I have Plesk (psa v8.0.1 RedHat el3) server running and get the following errors () in the Apache logs (/etc/httpd/logs/error_log)

[warn-phpd] mmap cache can't open /bla/bla/*.php - Too many open files (pid xx)

This error comes back for all PHP files

My customers receive al kind of PHP errors, and after a F5 it works again, 2 sec later it doesn’t

Is this because I have 519 (x2 = > 1024) Domains on the Plesk server? so the Apache limits should be raised? How can I do this? Are the Kernels which are ready to go? Are there other solutions by building one combined log for all 519 customers in stead of 519 x 2?

Thx in advance for helping out… :)
 
Similar problem, found some good solutions using Google here:

http://www.webhostingtalk.com/showthread.php?t=703147
http://support.theplanet.com/kb/ope...e-server-my-linux-server-and-seeing-error-mes
http://www.linuxquestions.org/quest...cant-open-foo.php-too-many-open-files-631033/

Bottom line:
In console, type ulimit -n to see current open file limit.

Edit the apache startup script, /etc/init.d/httpd and add this before anything else:

#Raise the ulimit
ulimit -n 20480

But if your server is already opening so many files you might want to consider the load on it ;-)
 
Back
Top