GNU bug report logs - #65178
[Shepherd] Non-responding service control fiber

Previous Next

Package: guix;

Reported by: Hilton Chain <hako <at> ultrarare.space>

Date: Wed, 9 Aug 2023 12:43:02 UTC

Severity: important

Merged with 65419

Done: Ludovic Courtès <ludo <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Hilton Chain <hako <at> ultrarare.space>
To: 65178 <at> debbugs.gnu.org
Cc: danclm <danclm <at> tutanota.com>, Robby Zambito <contact <at> robbyzambito.me>, Skyler Ferris <skyvine <at> protonmail.com>, Ignas Lapėnas <ignas <at> lapenas.dev>, Etienne B. Roesch <etienne.roesch <at> gmail.com>, Chris Keschnat <chris <at> catsu.it>
Subject: bug#65178: Shepherd hangs (was: Getting Guix to shutdown my laptop properly with Sway and no DE)
Date: Wed, 09 Aug 2023 20:41:44 +0800
Hello!

I have experienced many instances of Shepherd hanging through my use
of Guix, though I don't have a clear record of when it first happened.

These days I have seen a few reports on the subject.  With a quick
search of recent bug reports, I can't find any related, only to find
this thread [1] on help-guix.  So I'll start a bug report here, but I
don't know how to debug Shepherd and I haven't found a way to
reproduce it stably.

I'm not sure if Shepherd hangs at usual, but most of the time I find
it already hanging is when doing a reconfiguration.  The
reconfiguration becomes unresponsive and it won't accept a ^C, herd
actions also hang.  This usually happens with home reconfiguration,
but I can remember once with system reconfiguration when adding and
deleting some services in the configuration file.

I'm not sure how Shepherd hangs either, because in the latter case
(system one) I can still see logs indicating that it's trying to
respawn a process I killed manually, even though that's just a output
and no processes are actually spawned.

And as shown in [1], there are also cases where Shepherd hangs at some
point in the halting process, usually after syslogd has been
terminated but before term-tty*.

(The termination message indicates that Shepherd is still functional,
and no logs after that point shows that that's a real action, but
because of this I can't know anything happened further either.  After
that I'm still able to switch ttys so I assume term-tty* are alive.)

Although I don't know how they are related, I have linked my
configurations below:
<https://codeberg.org/hako/Testament/src/branch/trunk/dorphine-home.scm>
<https://codeberg.org/hako/Testament/src/branch/trunk/dorphine-system.scm>

Thanks

[1]:
<https://lists.gnu.org/archive/html/help-guix/2023-07/msg00021.html>
(public-inbox mirror on yhetil.org)
<https://yhetil.org/guix/NZXMeM4--3-9 <at> tutanota.com/t/#u>




This bug report was last modified 1 year and 140 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.