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

Issue errno: 24 "Too many open files"

SalvadorS

Regular Pleskian
Hello,

When I try to update the stats of the server manually I found a lot of errors like this:

statistics_collector[26678]: Failed to process database 'wordpress_b' from domain 'xxx.org': MySQL error 1018: Can't read dir of './wordpress_b/' (errno: 24 "Too many open files") executing query: SHOW TABLE STATUS FROM `wordpress_b`

I search in KB plex and found this:

https://kb.plesk.com/en/128643

I check what is the default number of limit open files:

mysqladmin -uadmin -p`cat /etc/psa/.psa.shadow` variables |grep -i open

| open_files_limit | 1024

I see the default is 1024, as the rest of the servers. My question is:

Can I know which domain/s are open the files? or files per domain? In order to check if the problem is with one particular domain?

As the server is with a few domains it is strange for me...

Thank you
 
Hi SalvadorS,


Can I know which domain/s are open the files? or files per domain? In order to check if the problem is with one particular domain?

To view the "open files for mysql - server" on Debian/Ubuntu based systems for example, you can use the command:

lsof | grep mysqld


Btw., there is absolutely nothing wrong to increase the ( low ) standard of 1024 open files. This limit is reached quite quickly, when you have several domains with several databases, which you will see, when you inspect the open files. ;)
 
Hi SalvadorS,

the limits should help against possible overusage and is not meant to be increased to a number, which could definetly harm your system, or which could bring your server on it's knees. ;)
Consider to double the standard setting and inspect your log - files regulary, to see if that fits your needs. If it doesn't, double it again... :)
 
Back
Top