From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.migadu.com ([2001:41d0:306:2d92::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms9.migadu.com with LMTPS id 8HFUDX5bzWScqAAASxT56A (envelope-from ) for ; Fri, 04 Aug 2023 22:11:42 +0200 Received: from aspmx1.migadu.com ([2001:41d0:306:2d92::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id AEE5DX5bzWSZHQAA9RJhRA (envelope-from ) for ; Fri, 04 Aug 2023 22:11:42 +0200 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 A92FB48160 for ; Fri, 4 Aug 2023 22:11:41 +0200 (CEST) Authentication-Results: aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=sfr.fr header.s=202006 header.b=PqevLO+B; spf=pass (aspmx1.migadu.com: domain of "bug-guix-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="bug-guix-bounces+larch=yhetil.org@gnu.org"; dmarc=none ARC-Seal: i=1; s=key1; d=yhetil.org; t=1691179902; a=rsa-sha256; cv=none; b=NbZ8qSG6hMlcGLjakFSgtHd6ZwL1Bnbad6N81tDMGf6BpMaeF+tDOpyiiD1DN2Ejcq3qZb JBK5gUB/gtIbyqVxKJfGtRi+MGS5ksadnDOxfClAYeQSbD98nGpjbLIBKZnnibE4dFiztm CXmAWFFWRsv2b489dWeH0eRwzGoXn9ImHfLhLAibZuDIv6yI5NvCGuk1Anbo7Q1GToridB oqzjHgec5M0rH/JcWo0fBvtf449nVLMnadSq8PyYJQ+QBOy8sI9uSRtezmSI1al8FNlGUm kgWEWKiGfsgj8645v7pIGtoGfrFX7KOhpagCoggPq10SPIWG9EnJNQABlRIBQQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1691179902; h=from:from:sender:sender:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type:resent-cc:resent-from:resent-sender: resent-message-id:in-reply-to:in-reply-to:references:references: list-id:list-help:list-unsubscribe:list-subscribe:list-post: dkim-signature; bh=RTA6bvBHYe+aYcuqIrZ3/cYhDglSSXZJO2CXbi98G88=; b=eqfBNStfXtdoGEOoQyyKceVLO201FYbjeuncl0VsQOIGGwnMokKMwfLVGw0iLGYk7RO5Ns G5PM616/hjF1cT/wVCDQOr8ukBlYy7XX4KYRcvxpB0hcWf0EwLdCsgkdjJ3GIojVB6gyPM x7NQk6d+6lvcp7mBsoUZrKx+GXXuA9fAtYJfssEhyovUIa9oS8kIW9GtcmwJJ2qvE+0Xpo EtHj81XfbEW48IvVRvV3q3SuI4L8AusxkWPOQ85p+ri8OfWsoTblj0qDxTuMrgvbaAdYMz coJCJxahNk8i1dFoaD7eRdYFLIDLXZ5E30n9DVyCV9bbWAoQJPwIL0eyKuAMMg== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=sfr.fr header.s=202006 header.b=PqevLO+B; spf=pass (aspmx1.migadu.com: domain of "bug-guix-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="bug-guix-bounces+larch=yhetil.org@gnu.org"; dmarc=none Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qS0Vr-0008CW-C0; Fri, 04 Aug 2023 15:31:03 -0400 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 1qQBxT-0003zj-To for bug-guix@gnu.org; Sun, 30 Jul 2023 15:20:04 -0400 Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1qQBxT-0003Qt-Lp for bug-guix@gnu.org; Sun, 30 Jul 2023 15:20:03 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1qQBxT-0006gt-Hk for bug-guix@gnu.org; Sun, 30 Jul 2023 15:20:03 -0400 X-Loop: help-debbugs@gnu.org Subject: bug#64455: shepherd: unable to use redefined system/system* in 0.10.1 References: In-Reply-To: Resent-From: urb59@sfr.fr Original-Sender: "Debbugs-submit" Resent-CC: bug-guix@gnu.org Resent-Date: Sun, 30 Jul 2023 19:20:03 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 64455 X-GNU-PR-Package: guix X-GNU-PR-Keywords: To: 64455@debbugs.gnu.org Received: via spool by 64455-submit@debbugs.gnu.org id=B64455.169074478325649 (code B ref 64455); Sun, 30 Jul 2023 19:20:03 +0000 Received: (at 64455) by debbugs.gnu.org; 30 Jul 2023 19:19:43 +0000 Received: from localhost ([127.0.0.1]:51258 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qQBx8-0006fZ-4B for submit@debbugs.gnu.org; Sun, 30 Jul 2023 15:19:43 -0400 Received: from smtp26.services.sfr.fr ([93.17.128.3]:45197) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qQA8S-0003ny-P8 for 64455@debbugs.gnu.org; Sun, 30 Jul 2023 13:23:18 -0400 X-mail-filterd: {"version":"1.7.1", "queueID":"4RDSrG20pKz1LQKd7", "contextId": "a8927d43-93c5-4dc8-8131-1053c43400a5"} Received: from wsfrf1445.priv.atos.fr (wsfrf1445.priv.atos.fr [91.224.149.200]) by msfrf2611.sfr.fr (SMTP Server) with ESMTP id 4RDSrG20pKz1LQKd7 for <64455@debbugs.gnu.org>; Sun, 30 Jul 2023 19:23:10 +0200 (CEST) X-mail-filterd: {"version":"1.7.1", "queueID":"4RDSrG1QYrz1LQKd6", "contextId": "c9418203-5854-4117-a0d4-4cb464d8c541"} X-sfr-mailing: LEGIT X-sfr-spamrating: 40 X-sfr-spam: not-spam DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=sfr.fr; s=202006; t=1690737790; h=Date:From:Reply-To:To:Subject; bh=RTA6bvBHYe+aYcuqIrZ3/cYhDgl SSXZJO2CXbi98G88=; b=PqevLO+BRFg9ZmN4fvN+cdE1Qw7snGfscvkNWjOoKJSUWh/LGlSWKGE NIOysK9OizZkYPYNVKE0C9LAjocBJU933pm1cZ2IOQTgX9F6h0wcup8n35aWNGSdogBgxJYnixSG YF7mthi6mzUyvQC2+paKVYl9KdbR+6WbQBbHDW3virMmXkh5whiWm4pJXKjELiQ0zFO5SF4OqL38 kGC43oFZLuFe3jrxl+F9miz/+JIy07jY2uKv8XMH79syt4RGVftEz3zR0P0902gcNQxM/iYwTXPm YAk1Gjk2kPbOWd4CgQYR8mPUG1KCmZWytp/x744D0mhVHILqYzw85PjmbXw== Received: from wsfrf1445.priv.atos.fr (wsfrf1445.priv.atos.fr [91.224.149.200]) (Authenticated sender: bernard.urban@sfr.fr) by msfrf2611.sfr.fr (SMTP Server) with ESMTPA id 4RDSrG1QYrz1LQKd6 for <64455@debbugs.gnu.org>; Sun, 30 Jul 2023 19:23:10 +0200 (CEST) Date: Sun, 30 Jul 2023 19:23:10 +0200 (CEST) From: urb59@sfr.fr Message-ID: <1745689920.43661.1690737790152@wsfrf1445.priv.atos.fr> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_43660_1966354539.1690737790152" X-ORIGINATING-IP: 91.224.149.200 X-Wum-Nature: EMAIL-NATURE X-SAVECOPY: true X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-REPLYTO: |~| X-Mailman-Approved-At: Sun, 30 Jul 2023 15:19:41 -0400 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-Mailman-Approved-At: Fri, 04 Aug 2023 15:31:00 -0400 X-BeenThere: bug-guix@gnu.org List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: urb59@sfr.fr Errors-To: bug-guix-bounces+larch=yhetil.org@gnu.org Sender: bug-guix-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US X-Migadu-Spam-Score: -4.13 X-Migadu-Scanner: mx2.migadu.com X-Migadu-Queue-Id: A92FB48160 X-Spam-Score: -4.13 X-TUID: 6iPphtinhRrh ------=_Part_43660_1966354539.1690737790152 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable =E2=80=8CHello, Sorry for the late reply, but release 0.10.2 didn't fix the issue. Current workaround: suppressing redefinition of system/system* and suppress= ing running tests/system-star.sh I am open to suggestions of how to help you debug that. Don't reply to buma2023, it was me, but it's a throw away address no longer= valid. >Hi, > >Ludovic Court=C3=A8s gnu.org> skribis: > >> "buma2023 outlook.fr" outlook.fr> skribis: >> >>> I am using happily shepherd since a few years as my init system on >>> Debian: amd64 (desktop and notebook), armhf (Cubox). >> >> Interesting!=C2=A0 I didn=E2=80=99t know of such uses. >> >>> I was using 0.9.1 with guile-3.0.5 and fibers-1.1.1. >>> >>> I recently tried 0.10.1 with guile-3.0.9 and fibers 1.3.1 and >>> encountered a problem with using system and system* in my services: >>> the simple fact to have the symbol system or system* in >>> /etc/shepherd.scm or included files (even if the command is not >>> executed) leads to a misbehaving shepherd, more specifically the >>> shepherd socket disappears; the system boots but with multiple >>> instances of the launched daemons. >>> >>> If a system/system* command is executed while booting, shepherd >>> blocks at the point of its execution. >>> >>> Example of service causing the failure: >>> >>> (register-services >>>=C2=A0 (make >>>=C2=A0=C2=A0=C2=A0 #:provides '(mytest) >>>=C2=A0=C2=A0=C2=A0 #:start (lambda args >>>=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0 (system "touch /tmp/somefile") >>>=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0 #t) >>>=C2=A0=C2=A0=C2=A0 )) >>> >>> The service is not started at boot, I have to do it manually afterwards= , >>> but I never can go there, as the shepherd socket is missing. >> >> I can reproduce it like this: >> >> $ cat /tmp/t.conf >> (register-services >>=C2=A0 (make >>=C2=A0=C2=A0=C2=A0 #:provides '(mytest) >>=C2=A0=C2=A0=C2=A0 #:start (lambda args >>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0 (system "touch /tmp/somefile") >>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0 #t))) >> >> (start 'mytest) >> $ shepherd -I -c/tmp/t.conf -s /tmp/sock >> Starting service root... >> Service root started. >> Service root running with value #t. >> Service root has been started. >> Starting service mytest... >>=C2=A0=C2=A0 C-c C-z >> [1]+=C2=A0 Stopped=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 shepherd -I -c/tmp/t.conf -s /tm= p/sock >> $ bg >> [1]+ shepherd -I -c/tmp/t.conf -s /tmp/sock & >> $ herd -s /tmp/sock status >> herd: error: /tmp/sock: Connection refused >> >> This is both with 0.10.1 and with >> d5ed516e736ce473902cc86b5cf4f61f27ebb642. > >Sorry, the bug is reproducible with 0.10.1 but *not* with >d5ed516e736ce473902cc86b5cf4f61f27ebb642. > >I believe this was fixed by Shepherd commit >2b310bd3b0ba0d7a08c77b456d34369cd6444edb (that is, after 0.10.1). > >I think I=E2=80=99ll release 0.10.2 within a couple of weeks, but it would= be >great if you could confirm that current Shepherd =E2=80=98master=E2=80=99 = works for you. > >Thanks! > >Ludo=E2=80=99. > Sincerely. --=20 Bernard=20 ------=_Part_43660_1966354539.1690737790152 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
=E2=80=8CHello,

Sorry for the late reply, but release 0.10.2 didn't fix the issue.

Current workaround: suppressing redefinition of system/system* and suppress= ing running tests/system-star.sh

I am open to suggestions of how to help you debug that.

Don't reply to buma2023, it was me, but it's a throw away address no longer= valid. 
>Hi,
>
>Ludovic Court=C3=A8s <ludo <at> gnu.org> skribis:
>
>> "buma2023 <at> outlook.fr" <buma2023 <at> outlook.f=
r> skribis:
>>
>>> I am using happily shepherd since a few years as my init syste=
m on
>>> Debian: amd64 (desktop and notebook), armhf (Cubox).
>>
>> Interesting!  I didn=E2=80=99t know of such uses.
>>
>>> I was using 0.9.1 with guile-3.0.5 and fibers-1.1.1.
>>>
>>> I recently tried 0.10.1 with guile-3.0.9 and fibers 1.3.1 and
>>> encountered a problem with using system and system* in my serv=
ices:
>>> the simple fact to have the symbol system or system* in
>>> /etc/shepherd.scm or included files (even if the command is no=
t
>>> executed) leads to a misbehaving shepherd, more specifically t=
he
>>> shepherd socket disappears; the system boots but with multiple
>>> instances of the launched daemons.
>>>
>>> If a system/system* command is executed while booting, shepher=
d
>>> blocks at the point of its execution.
>>>
>>> Example of service causing the failure:
>>>
>>> (register-services
>>>  (make <service>
>>>    #:provides '(mytest)
>>>    #:start (lambda args
>>>       (system "touch /tmp/somefile")
>>>       #t)
>>>    ))
>>>
>>> The service is not started at boot, I have to do it manually a=
fterwards,
>>> but I never can go there, as the shepherd socket is missing.
>>
>> I can reproduce it like this:
>>
>> $ cat /tmp/t.conf
>> (register-services
>>  (make <service>
>>    #:provides '(mytest)
>>    #:start (lambda args
>>           &=
nbsp;  (system "touch /tmp/somefile")
>>           &=
nbsp;  #t)))
>>
>> (start 'mytest)
>> $ shepherd -I -c/tmp/t.conf -s /tmp/sock
>> Starting service root...
>> Service root started.
>> Service root running with value #t.
>> Service root has been started.
>> Starting service mytest...
>>   C-c C-z
>> [1]+  Stopped        =
         shepherd -I -c/tmp/t.conf =
-s /tmp/sock
>> $ bg
>> [1]+ shepherd -I -c/tmp/t.conf -s /tmp/sock &
>> $ herd -s /tmp/sock status
>> herd: error: /tmp/sock: Connection refused
>>
>> This is both with 0.10.1 and with
>> d5ed516e736ce473902cc86b5cf4f61f27ebb642.
>
>Sorry, the bug is reproducible with 0.10.1 but *not* with
>d5ed516e736ce473902cc86b5cf4f61f27ebb642.
>
>I believe this was fixed by Shepherd commit
>2b310bd3b0ba0d7a08c77b456d34369cd6444edb (that is, after 0.10.1).
>
>I think I=E2=80=99ll release 0.10.2 within a couple of weeks, but it wo=
uld be
>great if you could confirm that current Shepherd =E2=80=98master=E2=80=
=99 works for you.
>
>Thanks!
>
>Ludo=E2=80=99.
>

Sincerely.

--=20

Bernard=20
------=_Part_43660_1966354539.1690737790152--