• 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.

NGINX does not start up -> Too Many Open Files

ehrenwert

Basic Pleskian
Hello,

at the moment NGINX is not willing to start:

The error:
Jan 09 17:39:01 lichtenberg.ehrenwert-webhosting.de nginx[5200]: nginx: [emerg] open() "/var/www/vhosts/system/example.com/logs/proxy_access_log" failed (24: Too many open files)

I tried to follow https://kb.odin.com/de/115139 to solve this but the error still appears:
ulimit -n
1000000

in NGINX.conf:

worker_rlimit_nofile 65536;

System is Debian 8 on Systemd.
 
I also mention a lot of errors in php5-fpm.log:

[09-Jan-2016 23:37:17] ERROR: failed to prepare the stderr pipe: Too many open files (24)

[09-Jan-2016 23:37:17] ERROR: failed to prepare the stderr pipe: Too many open files (24)

[09-Jan-2016 23:37:17] ERROR: failed to prepare the stderr pipe: Too many open files (24)

[09-Jan-2016 23:37:20] ERROR: failed to prepare the stderr pipe: Too many open files (24)

[09-Jan-2016 23:37:20] ERROR: failed to prepare the stderr pipe: Too many open files (24)

[09-Jan-2016 23:37:22] ERROR: failed to prepare the stderr pipe: Too many open files (24)

[09-Jan-2016 23:37:22] ERROR: failed to prepare the stderr pipe: Too many open files (24)

[09-Jan-2016 23:37:48] ERROR: failed to prepare the stderr pipe: Too many open files (24)

[09-Jan-2016 23:37:50] ERROR: failed to prepare the stderr pipe: Too many open files (24)

[09-Jan-2016 23:37:51] ERROR: failed to prepare the stderr pipe: Too many open files (24)
 
@ehrenwert,

I am pretty sure that you should remove the worker_rlimit_nofile directive.

In fact, this directive is overriding your limits configuration, for which the settings should be correct, in the sense that the value is high enough.

The Nginx override is resulting in a lower limit of open files (i.e. lower than the limit configuration allows).

Removing the Nginx override should do the trick, so it is worth the attempt.

Please change the Nginx settings and reload the Nginx reconfiguration.

Can you report back? I am rather curious whether the above solution helps.

Regards.....
 
Back
Top