unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: subashkc1 <subashkc1@protonmail.com>
Cc: unicorn-public@yhbt.net, Mike Perham <mike@perham.net>
Subject: Re: unicorn worker being killed issue
Date: Sat, 13 May 2023 00:10:43 +0000	[thread overview]
Message-ID: <20230513001043.M728368@dcvr> (raw)
In-Reply-To: <20230512080542.M758778@dcvr>

Eric Wong <e@80x24.org> wrote:
> FD=9 is the client socket, so it looks like you have a client
> that's opening a connection and not doing anything so recvfrom()
> fails and ppoll times out.  You'd need to track down why you
> have a client opening a connection like that.

Btw, this wouldn't be a problem in production with nginx in
front of unicorn (which is the only recommended production

nginx acts as a sponge to buffer the entire request (including
request body) since unicorn was never designed for slow clients,
malicious or not.

      reply	other threads:[~2023-05-13  0:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-06 22:02 unicorn worker being killed issue subashkc1
2023-05-07 23:13 ` Eric Wong
2023-05-10 21:34   ` subashkc1
2023-05-11 19:08     ` Eric Wong
2023-05-12  6:41       ` subashkc1
2023-05-12  8:05         ` Eric Wong
2023-05-13  0:10           ` Eric Wong [this message]

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:

  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=20230513001043.M728368@dcvr \
    --to=e@80x24.org \
    --cc=mike@perham.net \
    --cc=subashkc1@protonmail.com \
    --cc=unicorn-public@yhbt.net \


* 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


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).