From: "Ludovic Courtès" <ludo@gnu.org>
To: Mikael Djurfeldt <mikael@djurfeldt.com>
Cc: 40125@debbugs.gnu.org
Subject: bug#40125: Problem with guix offload: Remote channel closed
Date: Sat, 21 Mar 2020 16:50:41 +0100 [thread overview]
Message-ID: <87eetl1zce.fsf@gnu.org> (raw)
In-Reply-To: <CAA2XvwKrnhVRNykuXDtMvcqFAU7d0MRvaOF6xzhYCtQxu_5LPw@mail.gmail.com> (Mikael Djurfeldt's message of "Wed, 18 Mar 2020 21:01:36 +0100")
Hi Mikael!
Good to see you here. :-)
Mikael Djurfeldt <mikael@djurfeldt.com> skribis:
> mdj@hat:~$ guix offload test
> guix offload: testing 1 build machines defined in
> '/etc/guix/machines.scm'...
> guix offload: Guix is usable on 'wand.pdc.kth.se' (test returned
> "/gnu/store/883yjkl46dxw9mzykykmbs0yzwyxm17z-test")
> guix offload: 'wand.pdc.kth.se' is running GNU Guile 3.0.1
> sending 1 store item (0 MiB) to 'wand.pdc.kth.se'...
> exporting path `/gnu/store/gl7dps3yx0vrxz16sj7q3w7gs3vdbxj4-export-test'
> ;;; [2020/03/18 20:53:04.930901, 0] write_to_channel_port: [GSSH ERROR]
> Remote channel is closed: #<input-output: channel (open) 7f5ed680e780>
> Backtrace:
> 1 (primitive-load "/home/mdj/.config/guix/current/bin/guix")
> In guix/ui.scm:
> 1833:12 0 (run-guix-command _ . _)
>
> guix/ui.scm:1833:12: In procedure run-guix-command:
> Throw to key `guile-ssh-error' with args `("write_to_channel_port" "Remote
> channel is closed" #<input-output: channel (open) 7f5ed680e780> #f)'.
Did you generate a signing key on wand.pdc.kth.se? Specifically with:
sudo guix archive --generate-key
(See
<https://guix.gnu.org/manual/devel/en/html_node/Invoking-guix-archive.html>.)
Error reporting in guix offload is currently suboptimal as you have
seen. There’s a couple of bug reports open on that topic, so hopefully
we’ll get there soon!
Ludo’.
next prev parent reply other threads:[~2020-03-21 15:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 19:58 bug#40125: Problem with guix offload: Remote channel closed Mikael Djurfeldt
2020-03-18 20:01 ` Mikael Djurfeldt
2020-03-21 15:50 ` Ludovic Courtès [this message]
2020-03-21 16:05 ` Mikael Djurfeldt
2020-03-21 20:00 ` Mikael Djurfeldt
2020-03-21 22:16 ` Ludovic Courtès
2020-03-22 18:21 ` Mikael Djurfeldt
2020-03-22 20:45 ` Ludovic Courtès
2020-03-22 21:40 ` Mikael Djurfeldt
2020-03-22 21:56 ` Mikael Djurfeldt
2020-03-22 22:13 ` Mikael Djurfeldt
2020-03-22 22:14 ` Mikael Djurfeldt
2020-03-22 22:24 ` Mikael Djurfeldt
2020-03-22 22:30 ` Marius Bakke
2020-03-22 22:44 ` Mikael Djurfeldt
2020-03-22 22:58 ` Marius Bakke
2020-03-22 23:12 ` Mikael Djurfeldt
2020-03-22 23:28 ` Mikael Djurfeldt
2020-03-22 23:40 ` Marius Bakke
2020-03-23 9:50 ` Ludovic Courtès
2023-08-02 15: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=87eetl1zce.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=40125@debbugs.gnu.org \
--cc=mikael@djurfeldt.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).