Though I have done the following setting, and even restarted the server:
# head /etc/security/limits.conf -n2
www-data soft nofile -1
www-data hard nofile -1
# /sbin/sysctl fs.file-max
fs.file-max = 201558
The open files limitation of specific process is still 1024/4096:
# ps aux | grep nginx
root 983 0.0 0.0 85872 1348 ? Ss 15:42 0:00 nginx: master process /usr/sbin/nginx
www-data 984 0.0 0.2 89780 6000 ? S 15:42 0:00 nginx: worker process
www-data 985 0.0 0.2 89780 5472 ? S 15:42 0:00 nginx: worker process
root 1247 0.0 0.0 11744 916 pts/0 S+ 15:47 0:00 grep --color=auto nginx
# cat /proc/984/limits
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 8388608 unlimited bytes
Max core file size 0 unlimited bytes
Max resident set unlimited unlimited bytes
Max processes 15845 15845 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 15845 15845 signals
Max msgqueue size 819200 819200 bytes
Max nice priority 0 0
Max realtime priority 0 0
Max realtime timeout unlimited unlimited us
I've tried all possible solutions from googling but in vain. What setting did I miss?
For nginx simply editing
nginx.conf
and settingworker_rlimit_nofile
should change the limitation. I initially thought it is a self-imposed limit of nginx, but it increases limit per process:You can test by getting a nginx process ID (from
top -u nginx
), then run:To see the current limits
Another way on CentOS 7 is by
systemctl edit SERVICE_NAME
, add the variables there:save that file and reload the service.
On CentOS (tested on 7.x):
Create file
/etc/systemd/system/nginx.service.d/override.conf
with the following contents:Reload systemd daemon with:
Add this to Nginx config file:
And finally restart Nginx:
You can verify that it works with
cat /proc/<nginx-pid>/limits
.I found the answer in few minutes after posting this question...
/etc/security/limit.conf
is used by PAM, so it shoud be nothing to do withwww-data
(it's nologin user).