From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ludovic =?UTF-8?Q?Court=C3=A8s?= <ludo@gnu.org>
Subject: bug#38088: Guix system becomes unresponsive after backtrace
Date: Wed, 06 Nov 2019 18:42:37 +0100
Message-ID: <87y2wsvr3m.fsf@gnu.org>
References: <CAE4v=pib7J-rrcR9JDXN8iLdy2bMtUK+b7kPVMH4No35doRcGw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:470:142:3::10]:48634)
 by lists.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1iSPKg-00081x-TH
 for bug-guix@gnu.org; Wed, 06 Nov 2019 12:43:03 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1iSPKf-0008LM-VO
 for bug-guix@gnu.org; Wed, 06 Nov 2019 12:43:02 -0500
Received: from debbugs.gnu.org ([209.51.188.43]:60640)
 by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
 (Exim 4.71) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
 id 1iSPKf-0008KZ-SF
 for bug-guix@gnu.org; Wed, 06 Nov 2019 12:43:01 -0500
Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1iSPKf-0006ou-Or
 for bug-guix@gnu.org; Wed, 06 Nov 2019 12:43:01 -0500
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-Message-ID: <handler.38088.B38088.157306217326201@debbugs.gnu.org>
In-Reply-To: <CAE4v=pib7J-rrcR9JDXN8iLdy2bMtUK+b7kPVMH4No35doRcGw@mail.gmail.com>
 ("=?UTF-8?Q?G=C3=A1bor?= Boskovits"'s message of "Wed, 6 Nov 2019
 15:15:41 +0100")
List-Id: Bug reports for GNU Guix <bug-guix.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-guix>,
 <mailto:bug-guix-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/bug-guix>
List-Post: <mailto:bug-guix@gnu.org>
List-Help: <mailto:bug-guix-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-guix>,
 <mailto:bug-guix-request@gnu.org?subject=subscribe>
Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org
Sender: "bug-Guix" <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
To: =?UTF-8?Q?G=C3=A1bor?= Boskovits <boskovits@gmail.com>
Cc: 38088@debbugs.gnu.org

Hi G=C3=A1bor,

G=C3=A1bor 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 =E2=80=9Cbroken pipe=E2=80=
=9D when
=E2=80=98guix build=E2=80=99 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=E2=80=99.