<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">HI!</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div><div id="bloop_customfont" style="orphans: 2; widows: 2; margin: 0px;"><span style="color: rgb(0, 0, 0); font-family: Helvetica, Arial; font-size: 13px;">I think this log message is </span>irrelevant with the keepalive directive inside your upstream configuration block, it just tell you the connection was reset by the client side.</div> <div id="bloop_sign_1507010554367693056" class="bloop_sign"></div> <br><p class="airmail_on">On 3 October 2017 at 12:48:02, sachin.shetty@gmail.com (<a href="mailto:nginx-forum@forum.nginx.org">nginx-forum@forum.nginx.org</a>) wrote:</p> <blockquote type="cite" class="clean_bq"><span><div><div></div><div>Hi,
<br>
<br>I had an upstream defined in my config with keepalive 60. But the server is
<br>a legacy one and does not handle keep alive properly.
<br>
<br>So I removed the keepalive attribute and the errors I was seeing on the
<br>client from the upstream went away.
<br>
<br>But now I see a ton these info log lines:
<br>
<br>2017/10/03 04:37:51 [info] 1933#0: *6091340 recv() failed (104: Connection
<br>reset by peer) while sending to client, client: 164.40.242.212, server:
<br>kong, request: "POST
<br>/public-api/v1/fs/Shared/functional_tests_2017_10_03_06_37_49_068 HTTP/1.1",
<br>upstream:
<br>"http://10.116.4.42:7280/public-api/v1/fs/Shared/functional_tests_2017_10_03_06_37_49_068",
<br>host: "wdio.qa-egnyte.com"
<br>
<br>I dont see any functional errors in our system, and the info log seems
<br>harmless, but I was still curious to understand what this means and if it
<br>has any side effects at scale.
<br>
<br>Posted at Nginx Forum: https://forum.nginx.org/read.php?2,276657,276657#msg-276657
<br>
<br>_______________________________________________
<br>nginx mailing list
<br>nginx@nginx.org
<br>http://mailman.nginx.org/mailman/listinfo/nginx
<br></div></div></span></blockquote></body></html>