From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-2.9 required=3.0 tests=ALL_TRUSTED,AWL,BAYES_00, URIBL_BLOCKED shortcircuit=no autolearn=unavailable version=3.3.2 X-Original-To: unicorn-public@bogomips.org Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 7E4BC63382B; Tue, 24 Mar 2015 23:55:05 +0000 (UTC) Date: Tue, 24 Mar 2015 23:55:04 +0000 From: Eric Wong To: Michael Fischer Cc: unicorn-public Subject: Re: nginx reverse proxy getting ECONNRESET Message-ID: <20150324235504.GA16472@dcvr.yhbt.net> References: <20150324225437.GA21975@dcvr.yhbt.net> <20150324225957.GA22127@dcvr.yhbt.net> <20150324232320.GA9552@dcvr.yhbt.net> <20150324234620.GA15866@dcvr.yhbt.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150324234620.GA15866@dcvr.yhbt.net> List-Id: Eric Wong wrote: > ECONNRESET is harmless in this case (unless nginx started pipelining or > blindly attempting persistent connections to unicorn, which it should > not be doing since unicorn sends "Connection: close" on every response) Actually, are you getting 502 errors returned from nginx in this case? That would not be harmless. I suggest ensuring rack.input is fully-drained if that is the case (perhaps using PrereadInput).