Hello!

On Sat, Feb 16, 2013 at 03:43:55AM -0500, youreright wrote:

> I've tried to fix the "Too many connections problem" following the suggested
> sites:
> http://www.cyberciti.biz/tips/linux-procfs-file-descriptors.html
> http://www.cyberciti.biz/faq/linux-unix-nginx-too-many-open-files/#comment-79592
>
> I've ran into other seemingly nonsensical errors.
>
> I have a new unused server here where I’m trying to install/use nginx for
> php for the first time.
>
> Strange error for unused server?
> ==
> Firstly, it seems strange to me that I would get “Too many open files” for a
> new unused server. ulimit -Hn/Sn showed 4096/1024 which seemed adequate whie
> nginx was using only 9/10 acccording to: ls -l /proc//fd | wc -l
>
> Anyhow, I followed the instructions and now I get this error:
> ==
> 2013/02/15 16:30:39 [alert] 4785#0: 1024 worker_connections are not enough
> 2013/02/15 16:30:39 [error] 4785#0: *1021 recv() failed (104: Connection
> reset by peer) while reading response header from upstream, client:
> 127.0.0.1, server: localhost, request: “GET /info.php HTTP/1.0″, upstream:
> “http://127.0.0.1:80/info.php”, host: “127.0.0.1″
>
> Tried:
> ==
> I’ve tried increasing the worker_connections to large numbers e.g. 19999 to
> no avail.
>
> Any tips?

Error message (in particular, "127.0.0.1:80" as an upstream, and
"127.0.0.1" as a server) suggests you have proxy loop in your
configuration.

--
Maxim Dounin
http://nginx.com/support.html

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx