Info messages in the log: Connection reset by peer) while sending to client

[Zhang Chao]

HI!

I think this log message is irrelevant with the keepalive directive inside your upstream configuration block, it just tell you the connection was reset by the client side.

On 3 October 2017 at 12:48:02, sachin.shetty at gmail.com (nginx-forum at forum.nginx.org) wrote:

Hi,  

I had an upstream defined in my config with keepalive 60. But the server is  
a legacy one and does not handle keep alive properly.  

So I removed the keepalive attribute and the errors I was seeing on the  
client from the upstream went away.  

But now I see a ton these info log lines:  

2017/10/03 04:37:51 [info] 1933#0: *6091340 recv() failed (104: Connection  
reset by peer) while sending to client, client: 164.40.242.212, server:  
kong, request: "POST  
/public-api/v1/fs/Shared/functional_tests_2017_10_03_06_37_49_068 HTTP/1.1",  
upstream:  
"http://10.116.4.42:7280/public-api/v1/fs/Shared/functional_tests_2017_10_03_06_37_49_068",  
host: "wdio.qa-egnyte.com"  

I dont see any functional errors in our system, and the info log seems  
harmless, but I was still curious to understand what this means and if it  
has any side effects at scale.  

Posted at Nginx Forum: https://forum.nginx.org/read.php?2,276657,276657#msg-276657  

_______________________________________________  
nginx mailing list  
nginx at nginx.org  
http://mailman.nginx.org/mailman/listinfo/nginx  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20171003/a10faaeb/attachment.html>