unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: subashkc1 <subashkc1@protonmail.com>
To: "unicorn-public@yhbt.net" <unicorn-public@yhbt.net>
Subject: unicorn worker being killed issue
Date: Sat, 06 May 2023 22:02:45 +0000	[thread overview]
Message-ID: <w7BWN8IxeMKEPgZbrFk9i2_stHxvb4D-iE4-mpBKvyeLAZvEWS71ki3dsk4qYfjjqezWKdeNcRe8hGX0v96H8TszyPPNI1ktxN6Jwo61-X8=@protonmail.com> (raw)

Hey,

First of all, thanks for this awesome project.

I have a weird issue that I'm having trouble debugging. I've created a sample bare bones rails app where there issue is reproducible https://github.com/subashkc/sidekiq_webui_issue.

After running the rails app, and load up the sidekiq web UI, if I click on any tabs e.g. busy/queues then the request is served right away with a 200 but it seems there is a 2nd request (can't tell where from) which eventually times out and kills the unicorn worker.

I originally opened the issue with sidekiq repo but Mike (sidekiq owner) wasn't able to find anything wrong with sidekiq code and he suggested it seemed unicorn was double reading the request and the 2nd one dies after 60s timeout.

Warm Regards

Sent with Proton Mail secure email.

             reply	other threads:[~2023-05-06 22:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-06 22:02 subashkc1 [this message]
2023-05-07 23:13 ` unicorn worker being killed issue 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

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='w7BWN8IxeMKEPgZbrFk9i2_stHxvb4D-iE4-mpBKvyeLAZvEWS71ki3dsk4qYfjjqezWKdeNcRe8hGX0v96H8TszyPPNI1ktxN6Jwo61-X8=@protonmail.com' \
    --to=subashkc1@protonmail.com \
    --cc=unicorn-public@yhbt.net \
    /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).