guix deploy sometimes fail with error "failed to start Guile on remote host 'myhost'"

  • Open
  • quality assurance status badge
Details
2 participants
  • Ludovic Courtès
  • Maxim Cournoyer
Owner
unassigned
Submitted by
Maxim Cournoyer
Severity
normal
M
M
Maxim Cournoyer wrote on 2 Oct 2020 16:09
(name . bug-guix)(address . bug-guix@gnu.org)
871rigoh2v.fsf@gmail.com
Hello,

Sometimes 'guix deploy' ends up failing near the end, with what looks
like:

Toggle snippet (6 lines)
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.:

Toggle snippet (4 lines)
guix deploy: sending 8 store items (5 MiB) to 'myhost'...
guix deploy: successfully deployed mymachine

Thanks,

Maxim
L
L
Ludovic Courtès wrote on 2 Oct 2020 22:41
(name . Maxim Cournoyer)(address . maxim.cournoyer@gmail.com)(address . 43763@debbugs.gnu.org)
87pn60icmm.fsf@gnu.org
Hi Maxim,

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

Toggle quote (14 lines)
> 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:


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’.
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 43763@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 43763
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch