unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: 58926@debbugs.gnu.org
Subject: bug#58926: Shepherd becomes unresponsive after an interrupt
Date: Thu, 10 Nov 2022 10:59:23 +0100	[thread overview]
Message-ID: <87wn83jfk4.fsf@gnu.org> (raw)
In-Reply-To: <87a65cgo1t.fsf@gnu.org> (Mathieu Othacehe's message of "Mon, 31 Oct 2022 13:44:46 +0100")

Hi,

Mathieu Othacehe <othacehe@gnu.org> skribis:

> sudo herd restart service-that-hangs-upon-restart
>
>
> then hitting C-c, Shepherd becomes totally unresponsive:
>
> sudo herd status
>
>
> and all further Shpeherd commands hang forever. I was able to reproduce
> it in two different configurations:
>
> 1. On my laptop with a Wireguard service trying to reach a non-existing
> DNS server.
>
>             (service wireguard-service-type
>                      (wireguard-configuration
>                       (addresses (list "10.0.0.2/24"))
>                       (dns '("10.0.0.50")) #does not exit
>
> 2. On Berlin, while trying to restart nginx.

I experienced case #2: in that case ‘strace -p1’ showed that shepherd
was stuck on waitpid of the nginx process, which was not terminating.
Killing that process would unlock shepherd.

This might be <https://issues.guix.gnu.org/56674>.

Would be good to see what’s up with WireGuard.

Ludo’.




  reply	other threads:[~2022-11-10 10:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31 12:44 bug#58926: Shepherd becomes unresponsive after an interrupt Mathieu Othacehe
2022-11-10  9:59 ` Ludovic Courtès [this message]
2022-11-12 18:10 ` Ludovic Courtès
2022-11-17 10:23   ` bug#53225: " Ludovic Courtès
2022-11-12 18:28 ` Ludovic Courtès
  -- strict thread matches above, loose matches on Subject: below --
2022-07-20 21:39 bug#56674: [Shepherd] Use of ‘waitpid’, ‘system*’, etc. in service code can cause deadlocks Ludovic Courtès
2022-11-13 23:16 ` Ludovic Courtès
2022-11-14 16:32   ` bug#58926: Shepherd becomes unresponsive after an interrupt Ludovic Courtès

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=87wn83jfk4.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=58926@debbugs.gnu.org \
    --cc=othacehe@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 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).