unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Mikael Djurfeldt <mikael@djurfeldt.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 40125@debbugs.gnu.org
Subject: bug#40125: Problem with guix offload: Remote channel closed
Date: Sun, 22 Mar 2020 19:21:02 +0100	[thread overview]
Message-ID: <CAA2XvwJYu9rdZPOCTO54a4aLHFt8LngoDxtAVc151AnEcanjEw@mail.gmail.com> (raw)
In-Reply-To: <87pnd5wdyq.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 2703 bytes --]

I did this.

What is a bit strange is that the error message seemingly randomly alters
between what I already reported above and the following:

mdj@hat:~/prusa$ 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/kw12ny565xl5p05ag6ysgshc9mhh4rz2-export-test'
guix offload: error: unknown error while sending files over SSH

This error message is more common. In this case, I couldn't see anything
obviously strange except the following backtrace which contains strange
characters:

31963 write(2, "Backtrace:\n          13 (apply-smob/1 #<catch-closure
56464c2232a0>)\nIn ice-9/boot-9.scm:\n    718:2 12 (call-with-prompt
(\"prompt\") #<procedure 56464c2407e0 \342\200\246> \342\200\246)\nIn
ice-9/eval.scm:\n    619:8 11 (_ #(#(#<directory (guile-user)
56464c2c4750>)))\nIn ice-9/command-line.scm:\n   181:18 10 (_ #<input:
string 56464c2d2bd0>)\nIn unknown file:\n           9 (eval (begin
(use-modules (guix) (srfi srfi-34) # #) \342\200\246) #)\nIn
ice-9/eval.scm:\n   721:20  8 (primitive-eval (begin (use-modules (guix)
(srfi \342\200\246) \342"..., 1150 <unfinished ...>

I have also noticed that the above (the error message) happens inside the
function send-files. It is the last error clause at the end of the function
which reports the error message.

I'd like to be able to, e.g., modify the function send-files to give some
debugging output. How can I easily do that? Should I checkout guix with git
and try to run it in the source tree? Or do you have other suggestions?

Best regards,
Mikael

On Sat, Mar 21, 2020 at 11:16 PM Ludovic Courtès <ludo@gnu.org> wrote:

> Hi Mikael,
>
> Mikael Djurfeldt <mikael@djurfeldt.com> skribis:
>
> > I will look at the other buh reports. Meanwhile, do you have any hint on
> > where to look/insert logging code in order to see what is going on?
>
> On ‘wand’, can you run something like:
>
>   sudo strace -s 500 -p $(pidof sshd) -f -o sshd.log
>
> After that, run ‘guix offload test’ from the other host, and check what
> ‘sshd.log’ contains.  If would in particular look for all the ‘execve’
> syscalls as well as what happens right before ‘exit_group’ syscalls.
> There are probably error messages lurking there.  :-)
>
> You can share excerpts of the log but note that it will contain
> sensitive crypto material, so beware.
>
> Thanks in advance,
> Ludo’.
>

[-- Attachment #2: Type: text/html, Size: 3519 bytes --]

  reply	other threads:[~2020-03-22 18:22 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
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 [this message]
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=CAA2XvwJYu9rdZPOCTO54a4aLHFt8LngoDxtAVc151AnEcanjEw@mail.gmail.com \
    --to=mikael@djurfeldt.com \
    --cc=40125@debbugs.gnu.org \
    --cc=ludo@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).