GNU bug report logs - #71139
herd unresponsive on new 1.4.0 install

Previous Next

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

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

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

From: Antero Mejr <mail <at> antr.me>
To: bug-guix <at> gnu.org
Subject: herd unresponsive on new 1.4.0 install
Date: Thu, 23 May 2024 05:28:23 +0000

On a new Guix 1.4.0 install, I logged in and ran `herd status` to check
if sshd was running. However, the command blocked indefinitely with no
output. When I cancelled that and tried to shut the machine down with
`halt`, it also blocked and did nothing. The system was not being
reconfigured at the time.

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

From: Ludovic Courtès <ludo <at> gnu.org>
To: Antero Mejr <mail <at> antr.me>
Cc: 71139 <at> debbugs.gnu.org
Subject: Re: bug#71139: herd unresponsive on new 1.4.0 install
Date: Thu, 23 May 2024 11:35:04 +0200

Hi,

Antero Mejr <mail <at> antr.me> skribis:

> On a new Guix 1.4.0 install, I logged in and ran `herd status` to check
> if sshd was running. However, the command blocked indefinitely with no
> output. When I cancelled that and tried to shut the machine down with
> `halt`, it also blocked and did nothing. The system was not being
> reconfigured at the time.

Could it be that your system clock changed drastically, for instance in
response to ntpd synchronization?  There’s a bug when that happens:

  https://github.com/wingo/fibers/issues/89

Thanks,
Ludo’.

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

From: Antero Mejr <mail <at> antr.me>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 71139 <at> debbugs.gnu.org
Subject: Re: bug#71139: herd unresponsive on new 1.4.0 install
Date: Fri, 24 May 2024 18:36:13 +0000

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

> Could it be that your system clock changed drastically, for instance in
> response to ntpd synchronization?  There’s a bug when that happens:
>
>   https://github.com/wingo/fibers/issues/89

Yes I think that's it, since the machine was a server that hadn't done
an NTP sync before.

Perhaps we should consider using Fibers 1.1 for all architectures? This
problem occurred on a x86-64 machine. This issue reverted Fibers 1.3
just for ARM:
https://issues.guix.gnu.org/64966#6

Based on the Github discussion, it seems this bug isn't a priority for
the Fibers maintainers, and it has been an outstanding (and seemingly
common) issue for almost a year now.

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

From: Richard Sent <richard <at> freakingpenguin.com>
To: Antero Mejr <mail <at> antr.me>
Cc: Ludovic Courtès <ludo <at> gnu.org>, 71139 <at> debbugs.gnu.org
Subject: Re: bug#71139: herd unresponsive on new 1.4.0 install
Date: Sat, 25 May 2024 13:18:34 -0400

> Perhaps we should consider using Fibers 1.1 for all architectures? This
> problem occurred on a x86-64 machine. This issue reverted Fibers 1.3
> just for ARM:
> https://issues.guix.gnu.org/64966#6

With https://issues.guix.gnu.org/70892#3 Fibers is also reverted to 1.1
on RISC-V 64.

-- 
Take it easy,
Richard Sent
Making my computer weirder one commit at a time.

Previous Next

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