GNU bug report logs - #71173
‘static-networking’ service can remain in ‘starting’ state forever

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 71173 in the body.
You can then email your comments to 71173 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: bug-guix <at> gnu.org
Subject: ‘static-networking’ service can remain
 in ‘starting’ state forever
Date: Fri, 24 May 2024 16:42:00 +0200

The ‘static-networking’ service can remain in ‘starting’ state forever
when it specifies a nonexistent NIC.

This can be reproduced by running a system such as hydra/bayfront.scm
(in maintenance.git) in ‘guix system vm’: shepherd will wait for
‘networking’ to start forever, preventing the machine from being cleanly
halted.

I believe this is due to indefinite blocking in ‘network-set-up/linux’:

                 ;; Before going any further, wait for the
                 ;; device to show up.
                 (wait-for-link
                  #$(network-address-device address)
                  #:blocking? #f)

It should instead wait for a limited amount of time (info "(shepherd)
Defining Services").

Ludo’.

Message #8 received at 71173 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: 71173 <at> debbugs.gnu.org
Subject: Re: bug#71173: ‘static-networking’
 service can remain in ‘starting’ state forever
Date: Wed, 25 Dec 2024 22:38:17 +0100

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

> The ‘static-networking’ service can remain in ‘starting’ state forever
> when it specifies a nonexistent NIC.
>
> This can be reproduced by running a system such as hydra/bayfront.scm
> (in maintenance.git) in ‘guix system vm’: shepherd will wait for
> ‘networking’ to start forever, preventing the machine from being cleanly
> halted.
>
> I believe this is due to indefinite blocking in ‘network-set-up/linux’:
>
>                  ;; Before going any further, wait for the
>                  ;; device to show up.
>                  (wait-for-link
>                   #$(network-address-device address)
>                   #:blocking? #f)
>
> It should instead wait for a limited amount of time (info "(shepherd)
> Defining Services").

Proposed fix: <https://issues.guix.gnu.org/75100>.

Ludo'.

Message #13 received at 71173-done <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: 75100-done <at> debbugs.gnu.org, 71173-done <at> debbugs.gnu.org
Subject: Re: [bug#75100] [PATCH 0/3] Shepherd service of 'static-networking'
 completes in timely fashion
Date: Thu, 09 Jan 2025 00:25:21 +0100

Pushed:

  20a74ce28d tests: Run without the Linux kernel “quiet” argument.
  431ab10344 services: static-networking: Fail when devices don’t show up.
  8d649a8d17 services: static-networking: Run set-up/tear-down as a separate process.

Previous Next

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