2008/08/28 16:57:00 [alert] 14892#0: accept() failed (24: Too many open
files) while accepting new connection on 0.0.0.0:80
2008/08/28 16:57:00 [alert] 14892#0: accept() failed (24: Too many open
files) while accepting new connection on 0.0.0.0:80
2008/08/28 16:57:00 [alert] 14892#0: accept() failed (24: Too many open
files) while accepting new connection on 0.0.0.0:80
2008/08/28 16:57:00 [alert] 14892#0: accept() failed (24: Too many open
files) while accepting new connection on 0.0.0.0:80
2008/08/28 16:57:00 [alert] 14892#0: accept() failed (24: Too many open
files) while accepting new connection on 0.0.0.0:80
2008/08/28 16:57:00 [alert] 14892#0: accept() failed (24: Too many open
files) while accepting new connection on 0.0.0.0:80
2008/08/28 16:57:00 [alert] 14892#0: accept() failed (24: Too many open
files) while accepting new connection on 0.0.0.0:80
2008/08/28 16:57:00 [alert] 14892#0: accept() failed (24: Too many open
files) while accepting new connection on 0.0.0.0:80
2008/08/28 16:57:00 [alert] 14892#0: accept() failed (24: Too many open
files) while accepting new connection on 0.0.0.0:80
more and more error log as these,what is the problem?
♫
Hello,
your system is limiting the number of files that one user can open
(limit to 1024 for example).
You can for example increase that setting by adding an “ulimit -n 8192”
in the nginx startup script.
walt a écrit :
On Fri, Aug 29, 2008 at 11:17:22AM +0200, Robert G. wrote:
I think this should help: server_names_hash_bucket_size 128; you need
to add this at http { }
server_names_hash_bucket_size has no any relation to
2008/08/28 16:57:00 [alert] 14892#0: accept() failed (24: Too many open
files) while accepting new connection on 0.0.0.0:80
This is OS or process file limit.
I think this should help: server_names_hash_bucket_size 128; you need
to add this at http { }
My bad, but I had something similar to this, maybe it wasnt quite the
same error, but it was related to subdomains/vhosts and it worked. Sorry
