unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
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: Wed, 25 Mar 2015 09:48:28 +0000	[thread overview]
Message-ID: <CABHxtY4SUMvms7h=3U1_i9ja6hTGfoeF47FxH+GLvinjWN026Q@mail.gmail.com> (raw)
In-Reply-To: <20150324234620.GA15866@dcvr.yhbt.net>

On Tue, Mar 24, 2015 at 11:46 PM, Eric Wong <e@80x24.org> wrote:

>> Is it your hypothesis that the application is just failing to consume
>> the entire POST body in this instance?   In that case, wouldn't we
>> expect to see nginx failing to write on the socket instead of read?
>
> It could've been just big enough to fit inside the kernel socket
> buffers, but not enough for nginx to wait on.  In the below standalone
> example, the server only reads 4092 bytes of the 4096-byte request.

> Here's a bare-bones example without nginx/unicorn at all:

[snip]

Thank you for the example; it really zeroes in on the situation.  I
learn something new every day!

I'll check with the developers to find out whether the app is
misbehaving in a similar way.

Best regards,

--Michael


  parent reply	other threads:[~2015-03-25  9:48 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 [this message]
2015-03-24 23:02   ` Michael Fischer
  -- 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='CABHxtY4SUMvms7h=3U1_i9ja6hTGfoeF47FxH+GLvinjWN026Q@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).