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

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 38088 in the body.
You can then email your comments to 38088 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Gábor Boskovits <boskovits <at> gmail.com>
To: bug-guix <at> gnu.org
Subject: Guix system becomes unresponsive after backtrace
Date: Wed, 6 Nov 2019 15:15:41 +0100

[Message part 1 (text/plain, inline)]

Hello,

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.

Best regards,
g_bor
-- 
OpenPGP Key Fingerprint: 7988:3B9F:7D6A:4DBF:3719:0367:2506:A96C:CF63:0B21

[error_screenshot.png (image/png, attachment)]

Message #8 received at 38088 <at> debbugs.gnu.org (full text, mbox):

From: Danny Milosavljevic <dannym <at> scratchpost.org>
To: Gábor Boskovits <boskovits <at> gmail.com>
Cc: 38088 <at> debbugs.gnu.org
Subject: Re: bug#38088: Guix system becomes unresponsive after backtrace
Date: Wed, 6 Nov 2019 16:52:35 +0100

[Message part 1 (text/plain, inline)]

Hi Gábor,

On Wed, 6 Nov 2019 15:15:41 +0100
Gábor Boskovits <boskovits <at> gmail.com> wrote:

> 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.

Hmm, sounds like disk corruption.  If there's a sudden read-only appearing then
it's often because the kernel found a file system error and doesn't want to make
the situation worse.  It then remounts the affected file-system read-only.
According to the top of your screenshot, even /tmp is read-only.  I think we
don't use a tmpfs, so that's the root file system.

Could you check dmesg for signs?

[Message part 2 (application/pgp-signature, inline)]

Message #11 received at 38088 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Gábor Boskovits <boskovits <at> gmail.com>
Cc: 38088 <at> debbugs.gnu.org
Subject: Re: 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’.

Message #14 received at 38088 <at> debbugs.gnu.org (full text, mbox):

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

Hello,

Ludovic Courtès <ludo <at> gnu.org> ezt írta (időpont: 2019. nov. 6., Sze, 18:42):
>
> 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.)

Yes, it also became corrupted. fsck on boot fixed it.
Since then it works happily again...

>
> Could you check what happened on your machine?  Do /var/log/messages and
> /var/log/guix-daemon.log contain any hints?

No idea actually, I don't see anything really suspicious, but it might
well be that it just refused
to write to the logs also...

>
> Thanks,
> Ludo’.


Regards,
g_bor
-- 
OpenPGP Key Fingerprint: 7988:3B9F:7D6A:4DBF:3719:0367:2506:A96C:CF63:0B21

Message #17 received at 38088 <at> debbugs.gnu.org (full text, mbox):

From: Gábor Boskovits <boskovits <at> gmail.com>
To: Danny Milosavljevic <dannym <at> scratchpost.org>
Cc: 38088 <at> debbugs.gnu.org
Subject: Re: bug#38088: Guix system becomes unresponsive after backtrace
Date: Wed, 6 Nov 2019 23:42:30 +0100

Danny Milosavljevic <dannym <at> scratchpost.org> ezt írta (időpont: 2019.
nov. 6., Sze, 16:52):
>
> Hi Gábor,
>
> On Wed, 6 Nov 2019 15:15:41 +0100
> Gábor Boskovits <boskovits <at> gmail.com> wrote:
>
> > 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.
>
> Hmm, sounds like disk corruption.  If there's a sudden read-only appearing then
> it's often because the kernel found a file system error and doesn't want to make
> the situation worse.  It then remounts the affected file-system read-only.
> According to the top of your screenshot, even /tmp is read-only.  I think we
> don't use a tmpfs, so that's the root file system.

I also believe it was the root filesystem.

>
> Could you check dmesg for signs?

I believe the dmesg info was lost on force-restart. Logs contain nothing....

Regards,
g_bor
-- 
OpenPGP Key Fingerprint: 7988:3B9F:7D6A:4DBF:3719:0367:2506:A96C:CF63:0B21

Message #20 received at 38088 <at> debbugs.gnu.org (full text, mbox):

From: Giovanni Biscuolo <g <at> xelera.eu>
To: Gábor Boskovits <boskovits <at> gmail.com>
Cc: 38088 <at> debbugs.gnu.org
Subject: Re: bug#38088: Guix system becomes unresponsive after backtrace
Date: Thu, 07 Nov 2019 08:35:53 +0100

Hello Gabor,

Gábor Boskovits <boskovits <at> gmail.com> writes:

[...]

>> 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.)
>
> Yes, it also became corrupted. fsck on boot fixed it.
> Since then it works happily again...

if the problem depended on filesystem corruption and all is fine now for
you, could you also close this bug please?

[...]

Thanks! Gio'

-- 
Giovanni Biscuolo

Xelera IT Infrastructures

Message #25 received at 38088-done <at> debbugs.gnu.org (full text, mbox):

From: Gábor Boskovits <boskovits <at> gmail.com>
To: Giovanni Biscuolo <g <at> xelera.eu>
Cc: 38088-done <at> debbugs.gnu.org
Subject: Re: bug#38088: Guix system becomes unresponsive after backtrace
Date: Thu, 7 Nov 2019 08:40:10 +0100

It seems this was a filesystem corruption. Everything seems fine after reboot,
so closing.

Giovanni Biscuolo <g <at> xelera.eu> ezt írta (időpont: 2019. nov. 7., Cs, 8:36):
>
> Hello Gabor,
>
> Gábor Boskovits <boskovits <at> gmail.com> writes:
>
> [...]
>
> >> 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.)
> >
> > Yes, it also became corrupted. fsck on boot fixed it.
> > Since then it works happily again...
>
> if the problem depended on filesystem corruption and all is fine now for
> you, could you also close this bug please?
>
> [...]
>
> Thanks! Gio'
>
> --
> Giovanni Biscuolo
>
> Xelera IT Infrastructures



-- 
OpenPGP Key Fingerprint: 7988:3B9F:7D6A:4DBF:3719:0367:2506:A96C:CF63:0B21

Message #28 received at 38088 <at> debbugs.gnu.org (full text, mbox):

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

Hi Gábor,

Gábor Boskovits <boskovits <at> gmail.com> skribis:

> Ludovic Courtès <ludo <at> gnu.org> ezt írta (időpont: 2019. nov. 6., Sze, 18:42):
>>
>> 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.)
>
> Yes, it also became corrupted. fsck on boot fixed it.
> Since then it works happily again...

OK.  My guess is that there was maybe a transient error with your hard
disk, which led the kernel to remount the root file system read-only,
which in turn led to the failure of various programs, including
‘guix-daemon’.

I’m closing the bug, but do reopen it if you have reasons to suspect a bug!

Thanks,
Ludo’.

Previous Next

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