GNU bug report logs - #77610
guix-daemon socket activation does not work on the hurd

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: yelninei <at> tutamail.com
Subject: bug#77610: closed (Re: bug#77610: guix-daemon socket activation
 does not work on the hurd)
Date: Wed, 14 May 2025 17:05:09 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#77610: guix-daemon socket activation does not work on the hurd

which was filed against the guix package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 77610 <at> debbugs.gnu.org.

-- 
77610: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=77610
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Ludovic Courtès <ludo <at> gnu.org>
To: yelninei <at> tutamail.com
Cc: 77610-done <at> debbugs.gnu.org
Subject: Re: bug#77610: guix-daemon socket activation does not work on the hurd
Date: Wed, 14 May 2025 18:04:55 +0200

For the record, this issue is now fixed upstream:

  https://git.savannah.gnu.org/cgit/hurd/hurd.git/commit/?id=029ab7d7b38c76ba14c24fcbf526ccef29af9e88
  https://lists.gnu.org/archive/html/bug-hurd/2025-05/msg00016.html

Closing!

Ludo’.

[Message part 3 (message/rfc822, inline)]

From: yelninei <at> tutamail.com
To: bug-guix <at> gnu.org
Subject: guix-daemon socket activation does not work on the hurd
Date: Mon, 7 Apr 2025 18:29:29 +0200 (CEST)

Hi,

today i reconfigured my system and after a reboot I am unable to use the guix-daemon on a childhurd.


guix build hello -n
guix build: error: failed to connect to `/var/guix/daemon-socket/socket': Protocol error

Offloading:
guix offload: error: failed to connect over SSH to daemon at 'localhost', socket /var/guix/daemon-socket/socket

Daemon Logs:
socket-activated with 1 socket
unexpected build daemon error: reading from file: Resource temporarily unavailable
Starting the daemon as the root user normally continues to work as before so i suspect the socket activation change is to blame.
Guix commit: 6af680670bf9055b90e6f8b63c4c2ab7b08e7c56

Previous Next

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