From: "Ludovic Courtès" <ludo@gnu.org>
To: "Gábor Boskovits" <boskovits@gmail.com>
Cc: 38088@debbugs.gnu.org
Subject: bug#38088: Guix system becomes unresponsive after backtrace
Date: Wed, 06 Nov 2019 18:42:37 +0100 [thread overview]
Message-ID: <87y2wsvr3m.fsf@gnu.org> (raw)
In-Reply-To: <CAE4v=pib7J-rrcR9JDXN8iLdy2bMtUK+b7kPVMH4No35doRcGw@mail.gmail.com> ("Gábor Boskovits"'s message of "Wed, 6 Nov 2019 15:15:41 +0100")
Hi Gábor,
Gábor Boskovits <boskovits@gmail.com> skribis:
> I did not know how to get the info better, so here is a screenshot
> about the situation.
>
> This happened when I was trying a pre-inst-env guix build from a
> core-updates checkout.
> Previously python3 failed to build, and I was trying to build it again.
From the screenshot, it seems that your root file system (or at least
/tmp and /gnu/store) became read-only, which in turn caused various
things to fail, including guix-daemon (hence the “broken pipe” when
‘guix build’ was talking to it, I suppose.)
Could you check what happened on your machine? Do /var/log/messages and
/var/log/guix-daemon.log contain any hints?
Thanks,
Ludo’.
next prev parent reply other threads:[~2019-11-06 17:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 14:15 bug#38088: Guix system becomes unresponsive after backtrace Gábor Boskovits
2019-11-06 15:52 ` Danny Milosavljevic
2019-11-06 22:42 ` Gábor Boskovits
2019-11-06 17:42 ` Ludovic Courtès [this message]
2019-11-06 22:40 ` Gábor Boskovits
2019-11-07 7:35 ` Giovanni Biscuolo
2019-11-07 7:40 ` Gábor Boskovits
2019-11-07 20:58 ` 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
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=87y2wsvr3m.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=38088@debbugs.gnu.org \
--cc=boskovits@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).