• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Issue accept4() failed (24: Too many open files)

stevemartin

Basic Pleskian
iam getting error like this when i have 2k users online

[crit] 17583#0: accept4() failed (24: Too many open files) nginx error

[alert] 17583#0: *573920 socket() failed (24: Too many open files) while connecting to upstream

7y0W2QZ.png
 
Hi stevemartin,

pls. raise the general defined limits on your server ( /etc/security/limits.conf ) and consider to add unique settings, for nginx for example:

Code:
nginx           soft    nofile          64000
nginx           hard    nofile          64000
 
where to add it i dont see any option as nginx

Code:
# /etc/security/limits.conf
#
#This file sets the resource limits for the users logged in via PAM.
#It does not affect resource limits of the system services.
#
#Also note that configuration files in /etc/security/limits.d directory,
#which are read in alphabetical order, override the settings in this
#file in case the domain is the same or more specific.
#That means for example that setting a limit for wildcard domain here
#can be overriden with a wildcard setting in a config file in the
#subdirectory, but a user specific setting here can be overriden only
#with a user specific setting in the subdirectory.
#
#Each line describes a limit for a user in the form:
#
#<domain>        <type>  <item>  <value>
#
#Where:
#<domain> can be:
#        - a user name
#        - a group name, with @group syntax
#        - the wildcard *, for default entry
#        - the wildcard %, can be also used with %group syntax,
#                 for maxlogin limit
#
#<type> can have the two values:
#        - "soft" for enforcing the soft limits
#        - "hard" for enforcing hard limits
#
#<item> can be one of the following:
#        - core - limits the core file size (KB)
#        - data - max data size (KB)
#        - fsize - maximum filesize (KB)
#        - memlock - max locked-in-memory address space (KB)
#        - nofile - max number of open file descriptors
#        - rss - max resident set size (KB)
#        - stack - max stack size (KB)
#        - cpu - max CPU time (MIN)
#        - nproc - max number of processes
#        - as - address space limit (KB)
#        - maxlogins - max number of logins for this user
#        - maxsyslogins - max number of logins on the system
#        - priority - the priority to run user process with
#        - locks - max number of file locks the user can hold
#        - sigpending - max number of pending signals
#        - msgqueue - max memory used by POSIX message queues (bytes)
#        - nice - max nice priority allowed to raise to values: [-20, 19]
#        - rtprio - max realtime priority
#
#<domain>      <type>  <item>         <value>
#

#*               soft    core            0
#*               hard    rss             10000
#@student        hard    nproc           20
#@faculty        soft    nproc           20
#@faculty        hard    nproc           50
#ftp             hard    nproc           0
#@student        -       maxlogins       4

# End of file
 
Hi stevemartin,

as already suggested:
consider to add unique settings
for nginx for example
Code:
nginx           soft    nofile          64000
nginx           hard    nofile          64000
You can't find any UNIQUE settings for "nginx" in your "limits.conf", because YOU DIDN'T set them there. ;)

where to add it ...
As you can see, there are already some EXAMPLES ( commented with an "#" in front, so that you are able to understand, how unique settings may be configured and with my suggestion, you are now able to set a common, unique definition, which should work for most servers.

If, your question "where to add it" just requests, WHERE at the file "limits.conf" you should place the suggested definition, then the answer is => Where ever you would like to, because that doesn't matter. ;)


Btw... pls. make sure to RESTART the depending service, when you changed a limit for a system user, otherwise the service can't use the new setting and would still use the standard open-files-limit for all users, which is => "1024" .
 
Last edited by a moderator:
Back
Top