NGINX Access Logs

Hi guys,

I’m new to nginx. Can anyone explain what does - - - “-” “-” “-” “-” -
means in the access logs? Been getting lots of this in the log file.
Would like to know if this is the cause of nginx to show that there’s a
spike in traffic through the nginx graph. Example of log below:

[12/Feb/2014:11:25:28 +0800] “POST /…svc HTTP/1.1” 200 274 1.68 870
0.002 - - - “-” “-” “-” “-” -

HTTP/1.1" 200 274 1.68 869 0.026 0.006 - - - “-” “-” “-”

Posted at Nginx Forum:

On Sat, 2015-01-10 at 09:50 -0500, exilemirror wrote:

HTTP/1.1" 200 274 1.68 869 0.026 0.006 - - - “-” “-” “-” “-”

Posted at Nginx Forum:
NGINX Access Logs

look in your nginx.conf. I have the following line

log_format main ‘$remote_addr - $remote_user [$time_local]
'$status $body_bytes_sent “$http_referer” ’
‘“$http_user_agent” “$http_x_forwarded_for”’;

access_log /var/log/nginx/access.log;
error_log /var/log/nginx/error.log;

( sorry for the wrap )

Which itemises the fields. Obviously yours is different, but it’ll give
you the list.


Steve H. BSc(Hons) MIITP

Skype: sholdowa

nginx does not handle the TCP stack, which is part of the network layer
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
be responsible of the impossibility of opening new connections.

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

B. R.

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: