From: ludo@gnu.org (Ludovic Courtès)
To: Les Harris <les@lesharris.com>
Cc: guix-devel@gnu.org
Subject: Re: Offloading acquired build slot loop
Date: Wed, 06 May 2015 22:38:22 +0200 [thread overview]
Message-ID: <877fslqw5d.fsf@gnu.org> (raw)
In-Reply-To: <mi4kjc$959$1@ger.gmane.org> (Les Harris's message of "Sun, 03 May 2015 01:00:43 -0700")
Hi,
Les Harris <les@lesharris.com> skribis:
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Could you double-check whether this command succeeds as root and
>> non-interactively (no passphrase prompt):
>>
>> lsh -l USER build.server.com cat /proc/loadavg
>
> As a followup to this, this set me on the right track. Thank you! It is
> very obvious in hindsight but only my user could lsh into the build
> server, root did not have the needed key. Once that was fixed I could
> proceed.
Good to know. :-)
> I ran into two further issues that I have resolved.
>
> Issue 1) The offload build failed saying there was no code for module
> (guix config) because the build server guile could not find guix in its
> loadpath since I had installed guix to /usr/local I just symlinked in
> /usr/local/share/guile/site/2.0 to the right place in the /usr/share
> tree and this was resolved.
>
> Issue 2) The offload build failed with a permission denied error when
> trying to access the guix daemon's socket. The user local-guix was
> using to lsh into the build server did not have write permissions (it
> had read) on the socket file. Giving that user write permissions fixed
> this issue.
>
> So combine those three additional things with my initial setup and now I
> have functioning offloading.
Great. Well, I reckon this is a terrible user experience. :-/
> There are many hidden assumptions in setting up the offloading that I
> feel should be documented. Are documentation patches accepted?
Definitely, yes!
Thank you,
Ludo’.
prev parent reply other threads:[~2015-05-06 20:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-22 0:55 Offloading acquired build slot loop Les Harris
2015-04-22 21:18 ` Ludovic Courtès
2015-05-03 8:00 ` Les Harris
2015-05-06 20:38 ` Ludovic Courtès [this message]
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=877fslqw5d.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=les@lesharris.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).