On Tue, May 05, 2015 at 08:08:42AM -0400, Larry M. wrote:
uWSGI. Here, the /var/log/nginx/error_log is always empty. And the
see http://nginx.org/r/error_log. But I suspect it’s not what are
you looking for, see above.
When my app has, for example, a syntax error, then yes, that appears
in the uWSGI log. But what I was talking about are the HTTP errors
like a 500 or a 400. When I get those there’s nothing in the logs.
If an error is returned by your application and/or uWSGI, then its
reasons are expected to be in your application logs (or the uWSGI
If an error is returned by nginx (e.g., because a client sent an
invalid request and nginx returned 400), then reasons should be in
nginx error log. Client-related errors, though, are usually
logged at the “info” level, and won’t be visible in error log by
default, see http://nginx.org/r/error_log.
Note well that nginx error logs are highly customizeable, and it
is possible that you are looking into a wrong file. In
particular, please note that default error log can be redefined
during compilation (see “nginx -V” output to find out which one is
used by default), and can also be redefined on a per-server or a
per-location basis (check your configs to find out if it’s the