GNU bug report logs - #38088
Guix system becomes unresponsive after backtrace

Previous Next

Full log

View this message in rfc822 format

From: Ludovic Courtès <ludo <at> gnu.org>
To: Gábor Boskovits <boskovits <at> gmail.com>
Cc: 38088 <at> debbugs.gnu.org
Subject: bug#38088: Guix system becomes unresponsive after backtrace
Date: Wed, 06 Nov 2019 18:42:37 +0100

Hi Gábor,

Gábor Boskovits <boskovits <at> 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’.

Previous Next

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