From: Michael Fischer <mfischer@zendesk.com>
To: Eric Wong <e@80x24.org>
Cc: unicorn-public <unicorn-public@bogomips.org>
Subject: Re: nginx reverse proxy getting ECONNRESET
Date: Tue, 24 Mar 2015 23:02:46 +0000 [thread overview]
Message-ID: <CABHxtY7+dhCt39Qi6=+DWVd4oxpNMmWDZVe1a9rXKmtez6KAvw@mail.gmail.com> (raw)
In-Reply-To: <20150324225437.GA21975@dcvr.yhbt.net>
On Tue, Mar 24, 2015 at 10:54 PM, Eric Wong <e@80x24.org> wrote:
> Michael Fischer <mfischer@zendesk.com> wrote:
>> We have an nginx 1.6.2 proxy in front of a Unicorn 4.8.3 server that
>> is frequently reporting the following error:
>>
>> 2015/03/24 01:46:01 [error] 11217#0: *872231 readv() failed (104:
>> Connection reset by peer) while reading upstream
>>
>> The interesting things are:
>>
>> 1) The upstream is a Unix domain socket (to which Unicorn is bound)
>> 2) Unicorn isn't reporting that a child died in the error log (and I
>> verified their lifetimes with ps(1))
>>
>> Any hints as to what we should look for?
>
> What changed recently with your setup?
We upgraded nginx from 1.4.7 to 1.6.2. The frequency of the error has
increased significantly since. But I hesitate to point the finger at
nginx without more evidence, since its developers are very skilled.
> Which OS/kernel version + vendor version?
uname -3.13.0-40-generic #69~precise1-Ubuntu
Ruby 2.1.1
> Can you setup a test instance on a different nginx port/unicorn socket
> and with a config.ru such as:
>
> ------------------------- 8< ----------------------
> run(lambda do |env|
> $stderr.write("#$$ starting at #{Time.now}\n")
> # be sure to configure your unicorn timeout
> sleep
> # should not return, wait for unicorn to kill
> end)
> ----------------------------------------------------
>
> And hitting nginx with a single test request to reproduce the issue.
I'll take that step later if I have to, but I'm not sure what evidence
that would provide, since we're not having timeout issues -- when this
happens, the response time reported by nginx is usually just a few
seconds (Unicorn timeout is 90 seconds),
Thanks,
--Michael
next prev parent reply other threads:[~2015-03-24 23:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 22:43 nginx reverse proxy getting ECONNRESET Michael Fischer
2015-03-24 22:54 ` Eric Wong
2015-03-24 22:59 ` Eric Wong
2015-03-24 23:04 ` Michael Fischer
2015-03-24 23:23 ` Eric Wong
2015-03-24 23:29 ` Michael Fischer
2015-03-24 23:46 ` Eric Wong
2015-03-24 23:55 ` Eric Wong
2015-03-25 9:41 ` Michael Fischer
2015-03-25 10:12 ` Eric Wong
2015-03-25 9:48 ` Michael Fischer
2015-03-24 23:02 ` Michael Fischer [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-04-08 16:22 Gabe Martin-Dempesy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://yhbt.net/unicorn/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABHxtY7+dhCt39Qi6=+DWVd4oxpNMmWDZVe1a9rXKmtez6KAvw@mail.gmail.com' \
--to=mfischer@zendesk.com \
--cc=e@80x24.org \
--cc=unicorn-public@bogomips.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhbt.net/unicorn.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).