upstream (tcp stream mode) doesn't detect connecton failure

Cecile, Adam Adam.Cecile at hitec.lu
Mon Jan 8 12:37:41 UTC 2018


Hello,


I'm using this quite complicated setup involving SNI routing and proxy_protocol but I'm stuck on something.


Here is the configuration file:

http://paste.debian.net/hidden/62e13f9c/


Routing, proxy_protocol, logging stuff is working just fine, the only (quite critical issue) is that the "mag" upstream doesn't see connection failures and does not switch to the second server.


In the mag.log file I just see:

98.98.98.98 [08/Jan/2018:10:56:10 +0100] proxying to "mag":10.0.0.1:443 TCP 500 0 239 1.01


But instead of blacklisting this server and moving to 10.0.0.2 I receive a connection closed error on the client.


Thanks in advance for your help,


Best regards, Adam.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20180108/b1feb0de/attachment.html>


More information about the nginx mailing list