NGINX Access Logs

B.R. reallfqq-nginx at
Sun Jan 11 14:00:28 UTC 2015

nginx does not handle the TCP stack, which is part of the network layer of
the OSI stack, underneath anything nginx does.
Have a look at your OS network stack monitoring tools.

Exhaustion of TCP sockets (or file descriptors) will lead to the
impossibility of opening new connections and might lead to some
erratic/strange behavior, looking at the application level.
nginx might give a specific error message... or not. Loads of reasons might
be responsible of the impossibility of opening new connections.

Anyhow, use the proper tool to get the proper piece of information: that is
a logic proven to be robust.
*B. R.*

On Sun, Jan 11, 2015 at 9:11 AM, exilemirror <nginx-forum at> wrote:

> Hi Steve,
> Thanks for the reply. How do we determine if there's an overload of tcp
> connections via nginx?
> Is it via this access logs?
> Posted at Nginx Forum:
> _______________________________________________
> nginx mailing list
> nginx at
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the nginx mailing list