From: ludo@gnu.org (Ludovic Courtès)
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 31825@debbugs.gnu.org
Subject: bug#31825: guix offload fails with guix-authenticate error
Date: Mon, 18 Jun 2018 10:32:03 +0200 [thread overview]
Message-ID: <87zhzswl4s.fsf@gnu.org> (raw)
In-Reply-To: <87bmc87rlm.fsf@gmail.com> (Maxim Cournoyer's message of "Sun, 17 Jun 2018 22:31:33 -0400")
Hello,
Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:
> maxim@apteryx ~$ guix offload test
> guix offload: testing 1 build machines defined in '/etc/guix/machines.scm'...
> guix offload: '192.168.1.105' is running guile (GNU Guile) 2.2.3
> guix offload: Guix is usable on '192.168.1.105' (test returned "/gnu/store/883yjkl46dxw9mzykykmbs0yzwyxm17z-test")
> sending 1 store item to '192.168.1.105'...
> exporting path `/gnu/store/smgzvgc9krglk0mjpcscg5450l05w4dg-export-test'
> guix offload: error: build failed: program `guix-authenticate' failed
> with exit code 1
On closer inspection, it looks like it may be ‘guix-authenticate’ on
“apteryx” that fails. This could happen if there’s no signing key, for
instance, but you said there’s one, so I don’t know.
Could you attach strace to guix-daemon on “apteryx” and run “guix
offload test” again?
Use something like:
# strace -p $(pidof guix-daemon) -f -s 345 -o /tmp/log
and then:
# guix offload test
TIA,
Ludo’.
next prev parent reply other threads:[~2018-06-18 8:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-14 3:54 bug#31825: guix offload fails with guix-authenticate error Maxim Cournoyer
2018-06-14 22:08 ` Ludovic Courtès
2018-06-18 2:31 ` Maxim Cournoyer
2018-06-18 8:32 ` Ludovic Courtès [this message]
2018-06-19 2:35 ` Maxim Cournoyer
2018-06-19 9:28 ` Ludovic Courtès
[not found] ` <871sd354mb.fsf@gmail.com>
2018-06-19 14:49 ` Ludovic Courtès
2018-06-20 3:01 ` Maxim Cournoyer
2018-06-20 3:54 ` swedebugia
2018-06-22 2:13 ` Maxim Cournoyer
2018-06-20 14:06 ` Ludovic Courtès
2020-02-22 5:18 ` Maxim Cournoyer
2021-08-08 4:09 ` Maxim Cournoyer
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=87zhzswl4s.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=31825@debbugs.gnu.org \
--cc=maxim.cournoyer@gmail.com \
/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).