From: "Ludovic Courtès" <ludo@gnu.org>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: 45828@debbugs.gnu.org
Subject: bug#45828: guix build: error: got unexpected path `Backtrace:' from substituter
Date: Wed, 13 Jan 2021 14:51:52 +0100 [thread overview]
Message-ID: <87pn29aqrr.fsf@gnu.org> (raw)
In-Reply-To: <87o8htum2e.fsf@gnu.org> (Mathieu Othacehe's message of "Wed, 13 Jan 2021 12:13:13 +0100")
Hi,
Mathieu Othacehe <othacehe@gnu.org> skribis:
> There are errors in "/var/log/guix-publish.log" that could be the cause
> of this problem I think.
>
> GET /7m6mlzh0d6nifdxhaij7varg4q7lqdj4.narinfo
> In guix/scripts/publish.scm:
> 482:4 7 (render-narinfo/cached #<store-connection 256.99 7f916…> …)
> 487:12 6 (_ . _)
> In guix/store.scm:
> 1021:9 5 (_ #<store-connection 256.99 7f9165291230> "7m6mlzh0d6n…")
> 619:2 4 (write-buffered-output #<store-connection 256.99 7f9165…>)
> In unknown file:
> 3 (force-output #<output: string 7f91644a7690>)
> In guix/store.scm:
> 917:4 2 (write #vu8(29 0 0 0 0 0 0 0 32 0 0 0 0 0 0 0 55 109 …) …)
> In unknown file:
> 1 (put-bytevector #<input-output: socket 14> #vu8(29 0 …) …)
> In ice-9/boot-9.scm:
> 1669:16 0 (raise-exception _ #:continuable? _)
> In procedure fport_write: Broken pipe
As discussed on IRC today, the EPIPE above comes from talking to
guix-daemon, meaning that the store connection shown in the backtrace
has been closed by guix-daemon.
This can happen if guix-daemon was restarted but ‘guix publish’ wasn’t:
‘guix publish’ opens only one connection to the store at startup time,
and then never tries to re-open it. There was an old bug on this topic:
https://issues.guix.gnu.org/26705
Back then I marked it as ‘wontfix’ because:
1. Losing a connection to the daemon Does Not Happen™ in normal
conditions. Namely, upon ‘herd restart guix-daemon’, ‘guix
publish’ is automatically restarted. One situation where ‘guix
publish’ is not restarted is if one does “killall guix-daemon” or
similar. (Perhaps that’s something to fix in the Shepherd?)
2. Catching EPIPE in the right place is tricky. Basically we’d
probably need to install a 'system-error handler around each RPC
(and offer callers a way to choose the EPIPE handling strategy),
which would incur additional overhead.
Ludo’.
next prev parent reply other threads:[~2021-01-13 13:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 22:09 bug#45828: guix build: error: got unexpected path `Backtrace:' from substituter Leo Famulari
2021-01-12 22:46 ` Christopher Baines
2021-01-13 0:11 ` Julien Lepiller
2021-01-13 11:13 ` Mathieu Othacehe
2021-01-13 13:51 ` Ludovic Courtès [this message]
2021-01-14 9:09 ` Mathieu Othacehe
2021-01-13 13:52 ` Ludovic Courtès
2021-01-13 14:02 ` Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pn29aqrr.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=45828@debbugs.gnu.org \
--cc=othacehe@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.