Take the 2-minute tour ×  We recently had some 500's from nginx
itself that somehow were not logged (we have screenshots, but
nothing in the logs). That is weird in itself, because usually
errors show up there. Regardless, I am wondering if there is
something like a connection pool size that if maxed out would
result in a 500? We have correlated it potentially to a recent
spike in traffic, but it is not conclusive.  Anyone have any
ideas of how to begin to approach such an issue?  share|improve
this question The first two things you have to do are reproduce
this error and find out the reason why the Nginx doesn't log to
error_log. Also post your configuration file. –  quanta Oct 1
'11 at 11:25 add comment  2 Answers  up vote 3 down vote
accepted  We use a combination of log formats in nginx and lmon
to catch things like this. An NGINX log format like:  log_format
main '$status:$request_time:$upstream_response_time:$pipe:$body_
bytes_sent $connection $remote_addr $host $remote_user
[$time_local] "$request" "$ht