unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 43763@debbugs.gnu.org
Subject: bug#43763: guix deploy sometimes fail with error "failed to start Guile on remote host 'myhost'"
Date: Fri, 02 Oct 2020 22:41:53 +0200	[thread overview]
Message-ID: <87pn60icmm.fsf@gnu.org> (raw)
In-Reply-To: <871rigoh2v.fsf@gmail.com> (Maxim Cournoyer's message of "Fri, 02 Oct 2020 10:09:12 -0400")

Hi Maxim,

Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:

> Sometimes 'guix deploy' ends up failing near the end, with what looks
> like:
>
> guix deploy: sending 180 store items (1,094 MiB) to 'myhost'...
> [...] (progress bar)
> guix deploy: error: failed to deploy mymachine: failed to start Guile on
> remote host 'myhost'
>
>
> Upon retrying the same 'guix deploy' command, it usually succeeds, e.g.:
>
> guix deploy: sending 8 store items (5 MiB) to 'myhost'...
> guix deploy: successfully deployed mymachine

I’ve seen it too, and I think it might be the same issue as described
here:

  https://git.savannah.gnu.org/cgit/guix/maintenance.git/commit/?id=cdef930632d0a94b0d92bf4f5fc7227e75c6eb10

If that happens again, could you log in the target machine as root and
run:

  find ~/.cache/guile | xargs ls -lrtd

That way you’ll see if some .go files have just been compiled, and also
if there are temporary .go.XYZ files in there (stemming from an
interrupted compilation process due to the timeout.)

Thanks,
Ludo’.




      reply	other threads:[~2020-10-02 20:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-02 14:09 bug#43763: guix deploy sometimes fail with error "failed to start Guile on remote host 'myhost'" Maxim Cournoyer
2020-10-02 20:41 ` 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=87pn60icmm.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=43763@debbugs.gnu.org \
    --cc=maxim.cournoyer@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).