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

Previous Next

Package: guix;

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

Date: Fri, 24 May 2024 14:43:01 UTC

Severity: normal

To reply to this bug, email your comments to 71173 AT debbugs.gnu.org.

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

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to bug-guix <at> gnu.org:
bug#71173; Package guix. (Fri, 24 May 2024 14:43:01 GMT) Full text and rfc822 format available.
Acknowledgement sent to Ludovic Courtès <ludo <at> gnu.org>:
New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org. (Fri, 24 May 2024 14:43:01 GMT) Full text and rfc822 format available.

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’.
This bug report was last modified 146 days ago.

Previous Next

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