From: richard@freakingpenguin.com
To: 65463@debbugs.gnu.org
Subject: bug#65463: Herd `fport_write: Broken pipe` error when running `guix home reconfigure`
Date: Tue, 14 Nov 2023 20:55:26 -0500 [thread overview]
Message-ID: <87107ca490c719dd1e9c7a75915ceaa8@freakingpenguin.com> (raw)
In-Reply-To: <169277323322.1687.15739147838600524142@localhost>
Just throwing out that I'm also experiencing this issue, even with a
home configuration containing a single service, that being
home-gpg-agent-service. I've deployed the same configuration on two
different machines at the same checkout and only experience the issue on
one. The other machine works flawlessly. The only distinction between
the two is that the working machine is using Guix on a foreign
distribution while the nonworking machine is using Guix System.
I do see the same behavior mentioned previously such as herd commands
hanging. However, in my case there seems to be another negative symptom
from shepherd acting this way.
Various $ gpg commands will hang (presumably when they try invoking
gpg-agent). Trying to manually invoke $ gpg-agent --daemon fails and
hangs indefinitely without a message. This effectively makes gpg
unusable.
Barebones home-environment:
--8<---------------cut here---------------start------------->8---
(home-environment
(services
(list
(service home-gpg-agent-service-type
(home-gpg-agent-configuration
(pinentry-program
(file-append pinentry-tty "/bin/pinentry-tty"))
(ssh-support? #t))))))
--8<---------------cut here---------------end--------------->8---
herd status:
--8<---------------cut here---------------start------------->8---
Started:
+ gpg-agent
+ root
--8<---------------cut here---------------end--------------->8---
Interestingly when running $ gpg --card-status I see the following
printed to the log:
shepherd.log (nonworking machine):
--8<---------------cut here---------------start------------->8---
2023-11-14 19:23:06 Spawning systemd-style service
/gnu/store/2zgdxhbnkz8fgsb1l4xydm3nbvj66mih-gnupg-2.2.39/bin/gpg-agent.
2023-11-14 19:23:06 L2023-11-14 19:23:06 oading
/gnu/store/kzh1x4y030drw0jrdk08nynvvyasm3c1-shepherd.conf.
--8<---------------cut here---------------end--------------->8---
shepherd.log (working machine):
--8<---------------cut here---------------start------------->8---
2023-11-14 19:43:39 Spawning systemd-style service
/gnu/store/2zgdxhbnkz8fgsb1l4xydm3nbvj66mih-gnupg-2.2.39/bin/gpg-agent.
2023-11-14 19:43:39 Running value of service gpg-agent changed to 611.
2023-11-14 19:43:39 [gpg-agent] using fd 3 for ssh socket
(/run/user/1000/gnupg/S.gpg-agent.ssh)
2023-11-14 19:43:39 [gpg-agent] using fd 4 for browser socket
(/run/user/1000/gnupg/S.gpg-agent.browser)
2023-11-14 19:43:39 [gpg-agent] using fd 5 for extra socket
(/run/user/1000/gnupg/S.gpg-agent.extra)
2023-11-14 19:43:39 [gpg-agent] using fd 6 for std socket
(/run/user/1000/gnupg/S.gpg-agent)
2023-11-14 19:43:39 [gpg-agent] listing on: std=6 extra=5 browser=4
ssh=3)
--8<---------------cut here---------------end--------------->8---
For some reason shepherd is rereading its configuration file instead of
properly spawning the gpg-agent service. shepherd.conf and
shepherd-gpg-agent-ssh-agent.scm (a file that appears in shepherd.conf)
are identical between the two machines.
shepherd.conf (working and nonworking machine):
--8<---------------cut here---------------start------------->8---
(begin (use-modules (srfi srfi-34) (system repl error-handling)) (apply
register-services (map (lambda (file) (load file)) (quote
("/gnu/store/6zcvlihqs5mniw2vly4w7z39lhai2grz-shepherd-gpg-agent-ssh-agent.scm"))))
(action (quote root) (quote daemonize)) (format #t "Starting
services...~%") (let ((services-to-start (quote (gpg-agent ssh-agent))))
(if (defined? (quote start-in-the-background)) (start-in-the-background
services-to-start) (for-each start services-to-start)) (redirect-port
(open-input-file "/dev/null") (current-input-port))))
--8<---------------cut here---------------end--------------->8---
Sorry if this is too much or not helpful! First time on the mailing
list.
next prev parent reply other threads:[~2023-11-15 11:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 6:47 bug#65463: Herd `fport_write: Broken pipe` error when running `guix home reconfigure` Tanguy LE CARROUR
2023-09-09 16:09 ` Elias Kueny
2023-11-15 1:55 ` richard [this message]
2023-11-16 20:09 ` Richard Sent
2024-03-20 18:07 ` Ludovic Courtès
2024-03-21 19:27 ` Richard Sent
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87107ca490c719dd1e9c7a75915ceaa8@freakingpenguin.com \
--to=richard@freakingpenguin.com \
--cc=65463@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).