Nginx runs a year reported on this issue online offering, and for reasons not authorized to restart, but fortunately you can set
Logs being given as follows
2020/03/22 14:31:33 [crit] 19793#0: *2301 open() "/home/data/logs/access.log" failed (24: Too many open files), client: 101.227.140.37 2020/03/22 14:31:33 [crit] 19793#0: *2304 open() "/home/data/logs/access.log" failed (24: Too many open files), client: 101.227.140.44 2020/03/22 14:31:33 [crit] 19793#0: *2307 open() "/home/data/logs/access.log" failed (24: Too many open files), client: 101.227.140.43 2020/03/22 14:31:33 [crit] 19793#0: accept4() failed (24: Too many open files) 2020/03/22 14:31:33 [crit] 19793#0: accept4() failed (24: Too many open files) 2020/03/22 14:31:34 [crit] 19793#0: accept4() failed (24: Too many open files)
First check restrictions cat / proc / 3383 / limits Note the process ID of Kazakhstan is one of the nginx
Limit Soft Limit Hard Limit Units Max cpu time unlimited unlimited seconds Max file size unlimited unlimited bytes Max data size unlimited unlimited bytes Max stack size 10485760 unlimited bytes Max core file size 0 unlimited bytes Max resident set unlimited unlimited bytes Max processes 95709 95709 processes Max open files 1024 4096 files Max locked memory 65536 65536 bytes Max address space unlimited unlimited bytes Max file locks unlimited unlimited locks Max pending signals 95709 95709 signals Max msgqueue size 819200 819200 bytes Max nice priority 0 0 Max realtime priority 0 0 Max realtime timeout unlimited unlimited us
Obviously Max open files of Soft limit is too small to be set 4096
echo -n 'Max open files=4096:4096' > /proc/3383/limits
Nginx will be able to do the same process all normal broadcast