From: Attila Lendvai <attila@lendvai.name>
To: "67538@debbugs.gnu.org" <67538@debbugs.gnu.org>
Subject: bug#67538: Shepherd stops responding during "guix system reconfigure"
Date: Thu, 30 Nov 2023 11:23:56 +0000 [thread overview]
Message-ID: <zjz_MQz6LtUdw_h5FdaMW0sJTRPnOCh0GkjvqCPdaKOeHyIa1YI4WPdeXWUlf7iwgTh9U5Otcl9OZoIxsO-I9JiyxzTYWDo1zDiREEcma-0=@lendvai.name> (raw)
In-Reply-To: <2jFNivEClEPAr1CXZOBcuLfjxhZLnGqmelVGcxgU-iWgrw5scO18hnVBGeJVKSiCRAXpSH-KsMOAGjLtLZ-CjwPqdKwEdojXNxLhib04jaA=@lendvai.name>
> > my suspicion is that it's due to some error coming from a start
> > GEXP that somehow derails shepherd's event loop.
[...]
> iirc I once managed to get a debugger out when it happened and it's
> stuck waiting in one of the epoll/select/alike calls,
...or one of the start/stop GEXP's calls something that (sometimes?) blocks indefinitely (which violates the API of shepherd).
--
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
Child labor was not abolished, it was changed from productive work to counter-productive brainwashing, and made universal: compulsory public schooling.
next prev parent reply other threads:[~2023-11-30 11:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 21:37 bug#67538: Shepherd stops responding during "guix system reconfigure" Timo Wilken
2023-11-29 21:54 ` Attila Lendvai
2023-11-30 11:23 ` Attila Lendvai [this message]
2023-12-14 22:55 ` bug#67230: " Timo Wilken
2023-12-15 19:47 ` bug#65178: " Attila Lendvai
2023-12-15 20:33 ` bug#67230: " Timo Wilken
2023-12-15 21:24 ` bug#67538: " Attila Lendvai
2023-12-19 23:00 ` bug#65419: [Shepherd] Non-responding service control fiber Ludovic Courtès
2023-11-30 12:55 ` bug#67538: Shepherd stops responding during "guix system reconfigure" Simon Streit
2023-11-29 22:56 ` Michal Atlas
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='zjz_MQz6LtUdw_h5FdaMW0sJTRPnOCh0GkjvqCPdaKOeHyIa1YI4WPdeXWUlf7iwgTh9U5Otcl9OZoIxsO-I9JiyxzTYWDo1zDiREEcma-0=@lendvai.name' \
--to=attila@lendvai.name \
--cc=67538@debbugs.gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.