From: "Ludovic Courtès" <ludo@gnu.org>
To: Madhavan Krishnan <krishnanmadhavan000@gmail.com>
Cc: 48756@debbugs.gnu.org
Subject: bug#48756: guix offload: error: corrupt input while restoring archive from #<closed: file 7f68866bf770>
Date: Tue, 15 Jun 2021 11:24:56 +0200 [thread overview]
Message-ID: <87v96ftr87.fsf@gnu.org> (raw)
In-Reply-To: <87zgvsmv03.fsf@gmail.com> (Madhavan Krishnan's message of "Mon, 14 Jun 2021 14:33:00 +0100")
Hi,
Madhavan Krishnan <krishnanmadhavan000@gmail.com> skribis:
>> Does /etc/guix/signing-key.{pub,sec} exist on both machines?
>
>> You can generate it with ‘guix archive’ (info "(guix) Invoking guix
>> archive").
>
> Yes, the files are generated by
>
> #+begin_example
> sudo guix archieve --generate-key
> #+end_example
>
>
> /etc/guix/signing-key.pub
> /etc/guix/signing-key.sec
>
> and send the =signing-key.pub= to the build machine.
>
> #+begin_src shell
> sudo guix archieve --authorize< master/build.txt
> #+end_src
>
> both ways master <-> build
OK, so /etc/guix/acl exists on both machines, right?
Could you attach strace to sshd on the build machine:
sudo strace -p $(pidof sshd) -f -o /tmp/sshd.log -s 500
and then run this on the head machine:
sudo guix offload test
?
Looking at /tmp/sshd.log starting from the end might reveal an error
that occurs on the build machine.
You can share (part of) /tmp/sshd.log with me, but note that it may
contain sensitive material such as SSH secret keys or passwords.
Thanks,
Ludo’.
next prev parent reply other threads:[~2021-06-15 9:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-30 23:15 bug#48756: guix offload: error: corrupt input while restoring archive from #<closed: file 7f68866bf770> Madhavan Krishnan
2021-06-14 13:23 ` Ludovic Courtès
2021-06-14 13:33 ` Madhavan Krishnan
2021-06-15 9:24 ` Ludovic Courtès [this message]
[not found] ` <CAOeCqOKetOxjqBSsT4JbQSNscqOrzpCff1O1=j-ZHXWmNp6wmA@mail.gmail.com>
[not found] ` <87tuls9s9u.fsf@gnu.org>
[not found] ` <87fsxc5jcf.fsf@gmail.com>
[not found] ` <CAOeCqOJnqcd60ZVbsgUovAx-KD2y-C7NP++T7PVEK01w+JVc3A@mail.gmail.com>
[not found] ` <874kdq3tw9.fsf@gnu.org>
[not found] ` <87lf72f09x.fsf@gmail.com>
[not found] ` <87fsx8298i.fsf@gnu.org>
[not found] ` <CAOeCqOLqJXjGzsOh_vk+6gWxQAA-vM6VetEUX3=Yd1xdOuLrQA@mail.gmail.com>
[not found] ` <87mtrfty8c.fsf@gnu.org>
[not found] ` <CAOeCqO+chkb9WbXTWhbkgVrK88cUw78nR3sJdZWT_aaZwK+=OA@mail.gmail.com>
[not found] ` <8735t2z8pt.fsf@gnu.org>
[not found] ` <CAOeCqOJ2oehKV1jPGU_sXZmO1BnDRAJguBwgBVXR0QN6hMtyKQ@mail.gmail.com>
[not found] ` <87y2atun5t.fsf@gnu.org>
[not found] ` <878s2tarwd.fsf@gmail.com>
[not found] ` <87eeckra36.fsf@gnu.org>
[not found] ` <87k0mcaeo4.fsf@gmail.com>
[not found] ` <87lf6rpvrp.fsf@gnu.org>
[not found] ` <CAOeCqOL2NU8f9v8V5Tt3ur=EfjkUcV-BzW6SM-vX6NpRiHzcYA@mail.gmail.com>
2021-07-01 13:05 ` Ludovic Courtès
2021-07-01 13:19 ` Madhavan Krishnan
2021-07-22 1:46 ` 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=87v96ftr87.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=48756@debbugs.gnu.org \
--cc=krishnanmadhavan000@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).