herd unresponsive on new 1.4.0 install

  • Open
  • quality assurance status badge
Details
3 participants
  • Ludovic Courtès
  • Antero Mejr
  • Richard Sent
Owner
unassigned
Submitted by
Antero Mejr
Severity
normal
A
A
Antero Mejr wrote on 23 May 07:28 +0200
(address . bug-guix@gnu.org)
87zfshp05k.fsf@antr.me
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.
L
L
Ludovic Courtès wrote on 23 May 11:35 +0200
(name . Antero Mejr)(address . mail@antr.me)(address . 71139@debbugs.gnu.org)
87r0dsan1z.fsf@gnu.org
Hi,

Antero Mejr <mail@antr.me> skribis:

Toggle quote (6 lines)
> 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:


Thanks,
Ludo’.
A
A
Antero Mejr wrote on 24 May 20:36 +0200
(name . Ludovic Courtès)(address . ludo@gnu.org)(address . 71139@debbugs.gnu.org)
875xv3jbvm.fsf@antr.me
Ludovic Courtès <ludo@gnu.org> writes:

Toggle quote (5 lines)
> 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:

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.
R
R
Richard Sent wrote on 25 May 19:18 +0200
(name . Antero Mejr)(address . mail@antr.me)
87le3xstcl.fsf@freakingpenguin.com
Toggle quote (5 lines)
> 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#3Fibers is also reverted to 1.1
on RISC-V 64.

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

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 71139@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 71139
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch