GNU bug report logs - #43763
guix deploy sometimes fail with error "failed to start Guile on remote host 'myhost'"

Previous Next

Full log

Message #8 received at 43763 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Cc: 43763 <at> debbugs.gnu.org
Subject: Re: 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

Hi Maxim,

Maxim Cournoyer <maxim.cournoyer <at> 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’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.