From: "Ludovic Courtès" <ludo@gnu.org>
To: Hilton Chain <hako@ultrarare.space>
Cc: 65178@debbugs.gnu.org
Subject: bug#65178: Shepherd hangs (was: Getting Guix to shutdown my laptop properly with Sway and no DE)
Date: Sat, 02 Sep 2023 22:49:35 +0200 [thread overview]
Message-ID: <87a5u4e1wg.fsf_-_@gnu.org> (raw)
In-Reply-To: <87y1icmohn.wl-hako@ultrarare.space> (Hilton Chain's message of "Tue, 15 Aug 2023 21:20:04 +0800")
Hi!
Hilton Chain <hako@ultrarare.space> scribes:
> On Sun, 13 Aug 2023 23:25:59 +0800,
> Hilton Chain wrote:
>>
>> Today I encountered the home reconfiguration issue. The behavior is
>> similar to <https://issues.guix.gnu.org/54919>.
>
> And today Shepherd hung after starting a service [1], the service
> itself started successfully (process started, logs available):
I’m assuming this is shepherd 0.10.2, right?
> $ sudo herd enable cloudflare-tunnel && sudo herd start cloudflare-tunnel
> Enabled service cloudflare-tunnel.
>
> [1]: <https://codeberg.org/hako/Rosenthal/src/commit/c7dc95c2932d7362673c28cdc2f52e6bb8357c18/rosenthal/services/child-error.scm#L151>
Is any of the services you’re using doing “non-standard things” such as
using constructors/destructors other than those provided by shepherd
(‘make-forkexec-constructor’ et al.)?
Is it reproducible, and do you think you could come up with a reduce
test case (for example by removing services from the config until you
reach the minimum)?
Thanks,
Ludo’.
next prev parent reply other threads:[~2023-09-02 20:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <NZXMeM4--3-9@tutanota.com>
2023-08-09 12:41 ` bug#65178: Shepherd hangs (was: Getting Guix to shutdown my laptop properly with Sway and no DE) Hilton Chain via Bug reports for GNU Guix
2023-08-13 15:25 ` Hilton Chain via Bug reports for GNU Guix
2023-08-15 13:20 ` Hilton Chain via Bug reports for GNU Guix
2023-09-02 20:49 ` Ludovic Courtès [this message]
2023-09-03 8:21 ` Hilton Chain via Bug reports for GNU Guix
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a5u4e1wg.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=65178@debbugs.gnu.org \
--cc=hako@ultrarare.space \
/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://git.savannah.gnu.org/cgit/guix.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).