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: AS63949 45.79.64.0/19 X-Spam-Status: No, score=-3.2 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.6 Received: from ms.lwn.net (ms.lwn.net [45.79.88.28]) (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 037A71F4C4 for ; Tue, 12 Nov 2024 21:46:51 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (2048-bit key; unprotected) header.d=lwn.net header.i=@lwn.net header.a=rsa-sha256 header.s=20201203 header.b=f9fn+0G0; dkim-atps=neutral DKIM-Filter: OpenDKIM Filter v2.11.0 ms.lwn.net CA6EC403E9 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lwn.net; s=20201203; t=1731448011; bh=Vju3m1mj1vpbowGtqSX9VicM1TJ549G4G00SljM9C/g=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=f9fn+0G08kHtW1VH3uyLExjuZHV4wd5/ouvWgr/Mri5mlnb8I09iR+w/6cb3X5uGd ccnvA7aGLAdUz8WX7Qr9/D1RNU5JVCcxTZspSgGQMYuETZZaFeNKjQwHA9T8b4nFQm BleRUiOQ7P+ZrhZ/kRB5FSL5pOHpusIaI4AUHO1VCF1zxJ77CY31CS7fd99gorKsm3 +CSRJZ4TQ+AyGcRaYESRsxTt4FCJ2IZgSfshNhiH4VHKPq5jhzT9Wem9woR27yfOJT pSAwJaAdRYOCQwHLaS9PUUfGaL4pJ0PiaPkcEsQ01BCc50Tha3c2ltvkkLzLen3Ajn YMoFL/cDHeqsA== Received: from localhost (unknown [IPv6:2601:280:5e00:625::1fe]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ms.lwn.net (Postfix) with ESMTPSA id CA6EC403E9; Tue, 12 Nov 2024 21:46:50 +0000 (UTC) From: Jonathan Corbet To: Eric Wong Cc: meta@public-inbox.org Subject: Re: Occasional public-inbox-httpd flakiness In-Reply-To: <20241112214116.M819944@dcvr> References: <875xp15n3o.fsf@trenco.lwn.net> <20241105232445.M291444@dcvr> <87zfm4qn6t.fsf@trenco.lwn.net> <20241112192002.M245700@dcvr> <87o72kp2kz.fsf@trenco.lwn.net> <20241112214116.M819944@dcvr> Date: Tue, 12 Nov 2024 14:46:50 -0700 Message-ID: <87bjykp1kl.fsf@trenco.lwn.net> MIME-Version: 1.0 Content-Type: text/plain List-Id: Eric Wong writes: > Jonathan Corbet wrote: >> Eric Wong writes: >> > Jonathan Corbet wrote: >> >> Just to add a data point...the problem just recurred, and there are >> >> definitely cat-file processes running: >> >> >> >> $ ps ax | fgrep git >> >> 2640024 ? S 0:40 /usr/bin/git --git-dir=repos/ALL.git -c core.abbrev=40 cat-file --batch >> >> 2735080 ? S 0:18 /usr/bin/git --git-dir=repos/ALL.git -c core.abbrev=40 cat-file --batch >> >> 3184082 ? S 0:03 /usr/bin/git --git-dir=repos/ALL.git -c core.abbrev=40 cat-file --batch >> >> 3723223 ? Z 0:00 [git] >> >> 3723227 ? Z 0:00 [git] >> > >> > Can you see if the worker process causing warnings is connected to defunct gits? >> > Should've been fixed in master a while ago, but there's a lot of changes :x >> > master should be fine as long as you're not using -cindex + coderepos yet. >> >> By "connected to" you mean "is the parent of"? > > Yes. lsof +E should show how pipes are connecting processes. > Just wondering, those git zombies lingered until the restart, right? > > IOW, they didn't disappear after a few seconds if the -httpd > worker was busy with other things. During heavy traffic you'll > inevitably see short-lived zombies as the -httpd may not reap > fast enough, but zombies shouldn't linger indefinitely. Looking back through the terminal history, it looks like the zombies hung out for a bit, but then went away. There were a couple of zombies every time I looked, but the PIDs eventually changed. Thanks, jon