bug#38088: Guix system becomes unresponsive after backtrace

bug#38088: Guix system becomes unresponsive after backtrace

[Gábor Boskovits]

[-- Attachment #1: Type: text/plain, Size: 357 bytes --]

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

[-- Attachment #2: error_screenshot.png --]
[-- Type: image/png, Size: 40279 bytes --]

bug#38088: Guix system becomes unresponsive after backtrace

[Danny Milosavljevic]

[-- Attachment #1: Type: text/plain, Size: 674 bytes --]

Hi Gábor,

On Wed, 6 Nov 2019 15:15:41 +0100
Gábor Boskovits <boskovits@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?

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

bug#38088: Guix system becomes unresponsive after backtrace

[Gábor Boskovits]

Danny Milosavljevic <dannym@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@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

bug#38088: Guix system becomes unresponsive after backtrace

[Ludovic Courtès]

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

bug#38088: Guix system becomes unresponsive after backtrace

[Gábor Boskovits]

Hello,

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

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

bug#38088: Guix system becomes unresponsive after backtrace

[Giovanni Biscuolo]

Hello Gabor,

Gábor Boskovits <boskovits@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

bug#38088: Guix system becomes unresponsive after backtrace

[Gábor Boskovits]

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

Giovanni Biscuolo <g@xelera.eu> ezt írta (időpont: 2019. nov. 7., Cs, 8:36):
>
> Hello Gabor,
>
> Gábor Boskovits <boskovits@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

bug#38088: Guix system becomes unresponsive after backtrace

[Ludovic Courtès]

Hi Gábor,

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

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