On Sunday 02 November 2014 09:03:47 tunist wrote:
> thanks, looks like the same error message is buried in that change / code,
> yes - though i am no closer to discerning the original cause of the error
> being triggered, since i am not familiar with the nginx sourecode at this
> point.
> any tips are welcomed!
>

There's no way to find out what caused the error only by looking to standard
error message. You should provide the debug log at least.

See: http://nginx.org/en/docs/debugging_log.html

wbr, Valentin V. Bartenev

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx