From: ng0 <ng0@infotropique.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 27386@debbugs.gnu.org
Subject: bug#27386: offloading documentation and env
Date: Tue, 27 Jun 2017 14:54:18 +0000 [thread overview]
Message-ID: <20170627145418.iq54zrhfzbr7vdtn@abyayala> (raw)
In-Reply-To: <87injh5z3h.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 3612 bytes --]
Ludovic Courtès transcribed 2.8K bytes:
> ng0 <ng0@infotropique.org> skribis:
>
> > Ludovic Courtès transcribed 2.1K bytes:
> >> ng0 <ng0@infotropique.org> skribis:
> >>
> >> > And this is from master running an offloading test as it is right now.
> >> > Both ends have GuixSD.
> >> >
> >> > user@abyayala ~$ guix offload test
> >> > guix offload: testing 1 build machines defined in '/usr/local/etc/guix/machines.scm'...
> >> > guix offload: '192.168.1.179' is running guile (GNU Guile) 2.2.2
> >> > Backtrace:
> >> > 7 (primitive-load "/gnu/store/js4ml3w20ysh4znp9wl0da0ljji…")
> >> > In guix/ui.scm:
> >> > 1321:8 6 (run-guix-command _ . _)
> >> > In ice-9/boot-9.scm:
> >> > 837:9 5 (catch srfi-34 #<procedure 1cc6cc0 at guix/ui.scm:450:…> …)
> >> > 837:9 4 (catch system-error #<procedure 1cc6ce0 at guix/script…> …)
> >> > In guix/scripts/offload.scm:
> >> > 611:6 3 (check-machine-availability _ _)
> >> > In srfi/srfi-1.scm:
> >> > 656:11 2 (for-each #<procedure assert-node-has-guix (node name)> …)
> >> > In guix/scripts/offload.scm:
> >> > 543:2 1 (assert-node-has-guix #<node user@192.168.1.179:22555/…> …)
> >> > In ssh/dist/node.scm:
> >> > 397:8 0 (node-eval #<node user@192.168.1.179:22555/37146 1ceaa…> …)
> >> >
> >> > ssh/dist/node.scm:397:8: In procedure node-eval:
> >> > ssh/dist/node.scm:397:8: Throw to key `node-repl-error' with args `("Evaluation failed" "scheme@(guile-user)> While compiling expression:\nERROR: no code for module (guix)" ())'.
> >>
> >> This means that you need to make sure that the target machine has (guix)
> >> in its load path.
> >
> > I assume that you have read the rest of my messages and not just skipped
> > through them. I thought my messages were clear that (guix) is in the
> > loadpath, but only *locally* on the machine, not when connecting to it
> > via ssh.
>
> Right, this is why I suggested testing that *with a non-interactive
> connection*, as in:
>
> ssh HOST env | grep GUILE
>
> > So I'm guessing here: the not so obvious yet very obvious solution is to
> > put guix into the global (packages)?
> > Where global means the canonical /etc/config.scm
>
> On GuixSD, Guix is always in the global profile.
>
> >> The test is to run something like:
> >>
> >> $ ssh localhost env |grep GUILE_
> >> GUILE_LOAD_COMPILED_PATH=/home/ludo/.guix-profile/lib/guile/2.2/site-ccache:/home/ludo/.guix-profile/share/guile/site/2.2:/run/current-system/profile/lib/guile/2.2/site-ccache:/run/current-system/profile/share/guile/site/2.2
> >> GUILE_LOAD_PATH=/home/ludo/.guix-profile/share/guile/site/2.2:/run/current-system/profile/share/guile/site/2.2
> >>
> >> and you should see /run/current-system/profile/share/guile/site/2.2. If
> >> not, you’ll have to add it somehow.
>
> What does the above give for you?
>
> HTH,
> Ludo’.
This is issued from computer A (abyayala) to computer B (shadownet).
user@abyayala ~$ ssh shadownet env |grep GUILE_
GUILE_LOAD_COMPILED_PATH=/gnu/store/m91mxi586pi2qshzys9zfsmzij8nf547-profile/lib/guile/2.2/site-ccache:/gnu/store/m91mxi586pi2qshzys9zfsmzij8nf547-profile/share/guile/site/2.2
GUILE_LOAD_PATH=/gnu/store/m91mxi586pi2qshzys9zfsmzij8nf547-profile/share/guile/site/2.2
I would have to put some ssh private keys on there or
configure sshd in a different way to issue this locally
on computer B.
--
ng0
OpenPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
infotropique: https://www.infotropique.org
personal: https://ng-0.github.io https://krosos.org/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-06-27 14:55 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-15 17:05 bug#27386: offloading documentation and env ng0
2017-06-15 21:11 ` ng0
2017-06-15 22:19 ` ng0
2017-06-15 22:34 ` ng0
2017-06-26 19:56 ` Ludovic Courtès
2017-06-26 21:15 ` ng0
2017-06-27 13:39 ` Ludovic Courtès
2017-06-27 14:54 ` ng0 [this message]
2017-06-27 19:38 ` Ludovic Courtès
2017-06-27 20:31 ` ng0
2017-06-28 8:31 ` Ludovic Courtès
2017-06-28 11:45 ` ng0
2017-06-28 21:46 ` Ludovic Courtès
2017-06-28 22:36 ` ng0
2017-06-29 11:50 ` Ludovic Courtès
2017-07-04 13:51 ` Oleg Pykhalov
2017-07-04 15:43 ` Oleg Pykhalov
2017-07-04 16:02 ` Oleg Pykhalov
2017-07-04 21:36 ` Ludovic Courtès
2017-07-05 17:06 ` Oleg Pykhalov
2017-07-06 7:33 ` Ludovic Courtès
2017-07-06 13:15 ` Oleg Pykhalov
2017-07-07 10:00 ` Ludovic Courtès
[not found] ` <871spsginl.fsf@clover.i-did-not-set--mail-host-address--so-tickle-me>
2017-07-08 16:33 ` bug#27386: [SOLVED] " Ludovic Courtès
2017-09-28 19:40 ` Divan Santana
2017-09-28 19:44 ` Divan Santana
2017-09-29 7:49 ` Ludovic Courtès
2017-09-29 17:02 ` Ricardo Wurmus
2017-09-29 19:35 ` Divan Santana
2017-09-29 19:33 ` 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
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=20170627145418.iq54zrhfzbr7vdtn@abyayala \
--to=ng0@infotropique.org \
--cc=27386@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).