bug#58926: closed (Shepherd becomes unresponsive after an interrupt)

[GNU bug Tracking System]

Your message dated Thu, 17 Nov 2022 11:23:09 +0100
with message-id <87a64pkhgy.fsf@gnu.org>
and subject line Re: bug#58926: Shepherd becomes unresponsive after an interrupt
has caused the debbugs.gnu.org bug report #58926,
regarding Shepherd becomes unresponsive after an interrupt
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
58926: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=58926
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> Shepherd becomes unresponsive after an interrupt
>
>
>
>
> Date: 
>
> Mon, 31 Oct 2022 13:44:46 +0100
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux)
>
>
>
>
> Hello,
>
> When running the following command:
>
> --8<---------------cut here---------------start------------->8---
> sudo herd restart service-that-hangs-upon-restart
> --8<---------------cut here---------------end--------------->8---
>
> then hitting C-c, Shepherd becomes totally unresponsive:
>
> --8<---------------cut here---------------start------------->8---
> sudo herd status
> --8<---------------cut here---------------end--------------->8---
>
> 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.
>
> --8<---------------cut here---------------start------------->8---
>             (service wireguard-service-type
>                      (wireguard-configuration
>                       (addresses (list "10.0.0.2/24"))
>                       (dns '("10.0.0.50")) #does not exit
> --8<---------------cut here---------------end--------------->8---
>
> 2. On Berlin, while trying to restart nginx.
>
> In both situations, the "reboot" command was also hanging.
>
> Thanks,
>
> Mathieu
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#58926: Shepherd becomes unresponsive after an interrupt
>
>
>
>
> Date: 
>
> Thu, 17 Nov 2022 11:23:09 +0100
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux)
>
>
>
>
> Hi,
>
> Ludovic Courtès <ludo@gnu.org> skribis:
>
> > Mathieu Othacehe <othacehe@gnu.org> skribis:
> >
> >> 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
> >
> > This one is similar to:
> >
> >   https://issues.guix.gnu.org/53225
> >   https://issues.guix.gnu.org/53381
> >
> > It has to do with the fact that “wg-quick up” blocks until it succeeds
> > and that ‘invoke’ gets stuck on ‘waitpid’ until the “wg-quick” process
> > terminates.
> >
> > The solution will be to use something non-blocking instead of ‘invoke’;
> > I’m looking into it.
>
> This is fixed in the Shepherd 0.9.3, which landed in Guix commit
> 283d7318c5b312d7129adb6dbeea6ad205ce89d1.
>
> As I wrote, I’m not sure whether it fixes the nginx situation since I
> could not reproduce it.  I’m closing and let’s open a new issue
> specifically for nginx if it comes up again with 0.9.3.
>
> Thanks,
> Ludo’.
>
>
> --- End Message ---