Welcome! Log In Create A New Profile

Advanced

More Descriptive 502 Errors

April 02, 2014 03:44PM
Every so often I see a handful of errors in my error log, such as:

connect() failed (113: No route to host)
upstream timed out (110: Connection timed out)
upstream sent too big header while reading response header from upstream

etc.

in each case, when I log the $status variable in nginx, each just shows as a 502 error. Is there any way to retrieve what the actual error is (via variable?) without having to check the error log or is that the only source for this information?

Thanks!
Subject Author Posted

More Descriptive 502 Errors

abstein2 April 02, 2014 03:44PM

Re: More Descriptive 502 Errors

Maxim Dounin April 03, 2014 09:06AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 290
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready