Hello!
On Mon, Mar 02, 2015 at 09:11:11AM -0500, mastercan wrote:
> I've had 2 cases with status code 500 now since setting error log to debug
> level:
>
> The error msg: "epoll_wait() reported that client prematurely closed
> connection while sending request to upstream"
It's expected to be 49
I've had 2 cases with status code 500 now since setting error log to debug
level:
The error msg: "epoll_wait() reported that client prematurely closed
connection while sending request to upstream"
It's interesting to note that:
If a "normal" file (no caching involved) is requested and the client
Maxim Dounin Wrote:
> This makes me think that it is just a cached 500 response from
> your backend then. If in doubt, you can obtain details using
> debug log, see http://wiki.nginx.org/Debugging.
>
I also considered that, but then I'd need to have at least hundreds of 500
status codes since
Hello!
On Mon, Mar 02, 2015 at 07:50:46AM -0500, mastercan wrote:
> Maxim Dounin Wrote:
> ---
> > Hello!
> >
> > Try looking into the error log. When nginx returns 500, it used to
> > complain to the error log explaining the reason.
> >
>
>
Maxim Dounin Wrote:
---
> Hello!
>
> Try looking into the error log. When nginx returns 500, it used to
> complain to the error log explaining the reason.
>
Unfortunately the error log for that vhost does not reveal anything at the
specific t
Hello!
On Mon, Mar 02, 2015 at 06:11:24AM -0500, mastercan wrote:
> Hello,
>
> Nginx (all versions since September 2014, but at least 1.7.9, 1.7.10)
> sometimes returns HTTP status code 500, when serving pages from
> fastcgi_cache.
>
> Each time this happens, following conditions hold true:
> *
Hello,
Nginx (all versions since September 2014, but at least 1.7.9, 1.7.10)
sometimes returns HTTP status code 500, when serving pages from
fastcgi_cache.
Each time this happens, following conditions hold true:
*) $upstream_cache_status = HIT (so we don't even hit php-fpm)
*) $body_bytes_sent =
