• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

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