all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Divan Santana <divan@santanas.co.za>
Cc: Help guix <help-guix@gnu.org>
Subject: Re: Issues with guix offload
Date: Tue, 11 Jun 2019 12:22:38 +0200	[thread overview]
Message-ID: <87y3281kwh.fsf@gnu.org> (raw)
In-Reply-To: <87pnnuk87g.fsf@santanas.co.za> (Divan Santana's message of "Mon, 03 Jun 2019 17:19:15 +0200")

Hi Divan,

Did you eventually find out?

Divan Santana <divan@santanas.co.za> skribis:

> Not sure how to further troubleshoot it:
>
> ~ sudo guix offload test
> guix offload: testing 1 build machines defined in '/etc/guix/machines.scm'...
> guix offload: Guix is usable on 'cp3.santanas.co.za' (test returned "/gnu/store/883yjkl46dxw9mzykykmbs0yzwyxm17z-test")
> guix offload: 'cp3.santanas.co.za' is running GNU Guile 2.2.4
> sending 1 store item (0 MiB) to 'cp3.santanas.co.za'...
> exporting path `/gnu/store/sxxrzcpagpr87ldp82l9q634q7bbp8g5-export-test'
> guix offload: error: unknown error while sending files over SSH
>
> Seems something like this fails too
>
> guix copy --to=cp3.santanas.co.za emacs
>
> ~ ssh ds@cp3.santanas.co.za guile --version
> guile (GNU Guile) 2.2.4
>
> ~ ssh ds@cp3.santanas.co.za guix repl --version
> guix repl (GNU Guix) 1.0.1-3.4a54ed7
>
> Doing this (against sshd pid) on the build server results in a 2m file
> output. Where can I upload that?
>
> root@cp3 ~# strace -p 287 -s 300 -o log -f
>
> Not sure what to look for in the log output.

I would have suggested exactly this: look at the strace log, find the
bits that correspond to the ‘guix repl’ process, and see if there’s
anything wrong there.

Thanks,
Ludo’.

  reply	other threads:[~2019-06-11 10:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-03 15:19 Issues with guix offload Divan Santana
2019-06-11 10:22 ` Ludovic Courtès [this message]
2019-07-21  9:53   ` Divan Santana

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y3281kwh.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=divan@santanas.co.za \
    --cc=help-guix@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.