From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS62371 185.70.40.0/24 X-Spam-Status: No, score=-3.0 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM,RCVD_IN_MSPIKE_H2,SPF_HELO_PASS,SPF_PASS, T_SCC_BODY_TEXT_LINE shortcircuit=no autolearn=ham autolearn_force=no version=3.4.6 Received: from mail-4027.protonmail.ch (mail-4027.protonmail.ch [185.70.40.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 5DC331F406 for ; Sat, 6 May 2023 22:02:58 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (2048-bit key; secure) header.d=protonmail.com header.i=@protonmail.com header.a=rsa-sha256 header.s=protonmail3 header.b=qR2Zu2NU; dkim-atps=neutral Date: Sat, 06 May 2023 22:02:45 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1683410576; x=1683669776; bh=IlohrdnZiC2Ur0AYmLn064QkmHzsVnkWWWqjNyBnl5M=; h=Date:To:From:Subject:Message-ID:Feedback-ID:From:To:Cc:Date: Subject:Reply-To:Feedback-ID:Message-ID:BIMI-Selector; b=qR2Zu2NUhPXn79ptZEL6FXagcNqXLi3oy4jAkEbRLbAw6OZV/cfxiwR+4Kk7tgtmE fJQisL1medFiTql+u2yoiKrLfvGhhb3XcqOxLFRRJ1LrRM1ZhHLWG1etBf+acWWssC mYGHJbVNxLatmnFcbUKHqvohGePtY/JSizC+6ySjNHIEDNZ4ALqyWu0VEPUDEsi9xj ee+Hdu9tXIar9FGd5YGSb3QWqB/5/uIowKCiB2poSDPVB/RZppdwFbGpVplL9XmwNF 6fWftPJDIZC8Apu06WGWZBdGP0fW1smP2tdCfKzqrr0/r9pL18j6b4PxLfMyxz0QMQ nHkojDcnB+z8g== To: "unicorn-public@yhbt.net" From: subashkc1 Subject: unicorn worker being killed issue Message-ID: Feedback-ID: 16972922:user:proton MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: Hey, First of all, thanks for this awesome project. I have a weird issue that I'm having trouble debugging. I've created a samp= le bare bones rails app where there issue is reproducible https://github.co= m/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 eventuall= y times out and kills the unicorn worker. I originally opened the issue with sidekiq repo but Mike (sidekiq owner) wa= sn't able to find anything wrong with sidekiq code and he suggested it seem= ed unicorn was double reading the request and the 2nd one dies after 60s ti= meout. Warm Regards Sent with Proton Mail secure email.