From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2.migadu.com ([2001:41d0:303:e16b::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms13.migadu.com with LMTPS id 2BFSHrhZS2cjBAAAe85BDQ:P1 (envelope-from ) for ; Sat, 30 Nov 2024 18:30:16 +0000 Received: from aspmx1.migadu.com ([2001:41d0:303:e16b::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2.migadu.com with LMTPS id 2BFSHrhZS2cjBAAAe85BDQ (envelope-from ) for ; Sat, 30 Nov 2024 19:30:16 +0100 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gnu.org header.s=fencepost-gnu-org header.b=ghlygkqn; dmarc=pass (policy=none) header.from=gnu.org; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org" Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 6330179E14 for ; Sat, 30 Nov 2024 19:30:11 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tHSDk-0003EJ-PB; Sat, 30 Nov 2024 13:29:33 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tHSDj-0003E8-50 for guix-devel@gnu.org; Sat, 30 Nov 2024 13:29:31 -0500 Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tHSDi-0001Ks-LO; Sat, 30 Nov 2024 13:29:30 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-Version:Date:References:In-Reply-To:Subject:To: From; bh=14UkG8Bx2dixXL3/foU6uE24Wgak6Thhxa5dgAYrEuQ=; b=ghlygkqnTPcNQKqyPFVB UMljlD1PsptCykobZaQGZDMjcJ5LWFY/IEAh98IHLK+AXI9TKqI0a6qwwAmEavjvU9HAVDA3CHONW je9Q0KQmtZzLAj/mldz4ASBDyNxqwFTIgKO4g4TT4+lyFljez4CS2rqKIVhFDtPvH9aQrNL4p+a4C qaXo9L8F5A03mQUgCjyhPjhq/Q7Ok6riEunAF39kldefCWaRQ+n1pZdBXt8sB1034u6MzY1MQ/olV e71LNHrDMq6YqxYUW38fYd4WoXA3Cx4O8oQbAgQXNuRkuy+1G8GPH6Xf0BpZ8gSSk6BLqscp4/Yuk zlm3nbJL3dkx1A==; From: =?utf-8?Q?Ludovic_Court=C3=A8s?= To: Attila Lendvai Cc: guix-devel Subject: Re: shepherd: failing test: should `herd stop` stop a respawning process? In-Reply-To: (Attila Lendvai's message of "Fri, 22 Nov 2024 20:43:41 +0000") References: <87bjza4mee.fsf@gnu.org> X-URL: http://www.fdn.fr/~lcourtes/ X-Revolutionary-Date: =?utf-8?Q?D=C3=A9cadi?= 10 Frimaire an 233 de la =?utf-8?Q?R=C3=A9volution=2C?= jour de la Pioche X-PGP-Key-ID: 0x090B11993D9AEBB5 X-PGP-Key: http://www.fdn.fr/~lcourtes/ludovic.asc X-PGP-Fingerprint: 3CE4 6455 8A84 FDC6 9DB4 0CFB 090B 1199 3D9A EBB5 X-OS: x86_64-pc-linux-gnu Date: Sat, 30 Nov 2024 19:29:26 +0100 Message-ID: <87bjxwy3qx.fsf@gnu.org> User-Agent: Gnus/5.13 (Gnus v5.13) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org Sender: guix-devel-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US X-Migadu-Queue-Id: 6330179E14 X-Migadu-Scanner: mx13.migadu.com X-Migadu-Spam-Score: -6.17 X-Spam-Score: -6.17 X-TUID: Q5OrqBWStd+s Hi Attila, Attila Lendvai skribis: > ok, i've attached a stipped down version of the test case. it hopefully r= eproduces the same situation i'm observing on my servers. > > which seems to be the following: > > 1. i have a service that keeps respawning (typically due to a config > mistake) > > 2. said service is upgraded/replaced in a `guix system reconfigure` > > 3. v1 of the service keeps respawning forever, and there's nothing i > can do to stop it at this point. `herd disable` operates on v2 of > the service, while some fiber, or some signal handler of v1 is > still in a respawn loop. Thanks for the detailed bug report and test case. It=E2=80=99s a pretty na= sty bug that you found here. Commit 5fe594d593e6dcb19e23029bf3ff5f4a77a92523 should fix it. Let me know if you notice anything wrong! Ludo=E2=80=99.