GNU bug report logs - #35532
guix-daemon was freezed

Previous Next

Package: guix;

Reported by: znavko <at> disroot.org

Date: Thu, 2 May 2019 05:46:01 UTC

Severity: normal

Done: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>

Bug is archived. No further changes may be made.

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

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

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-guix <at> gnu.org:
bug#35532; Package guix. (Thu, 02 May 2019 05:46:01 GMT) Full text and rfc822 format available.

Acknowledgement sent to znavko <at> disroot.org:
New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org. (Thu, 02 May 2019 05:46:02 GMT) Full text and rfc822 format available.

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

From: znavko <at> disroot.org
To: "bug-guix" <bug-guix <at> gnu.org>
Subject: guix-daemon was freezed
Date: Thu, 02 May 2019 05:44:06 +0000
[Message part 1 (text/plain, inline)]
Yesterday, I ran updates with `guix pull && guix package -u`. My laptop warked all night long.
But this morning, I've discovered the update process stops without life on this step:

$ guix pull && guix package -u
...
downloading from https://ci.guix.info/nar/gzip/zqfbh4whwrzzhqa811i43dggyqh2lmwx-libevent-2.1.8...
 libevent-2.1.8 787KiB 787KiB/s 00:01 [##################] 100.0%

building /gnu/store/9y4j59sbxg9igj774q8r04vz31c5clrc-bitcoin-core-0.17.1.drv...
substitute: updating substitutes from 'https://ci.guix.info'... 100.0%
substitute: updating substitutes from 'https://ci.guix.info'... 100.0%

I think the Internet connection was the reason.
I stopped guix process and tryed to delete bitcoin-core, but this was not going again:

$ guix package -r bitcoin-core
The following package will be removed:
 bitcoin-core 0.17.1 /gnu/store/3gi4m4c2x1hybxlxnh5ll7s474mzz0lj-bitcoin-core-0.17.1

^C^C

After that I typed remove fluidsynth in other terminal and the process was not going again:

$ guix package -r fluidsynth
The following package will be removed:
 fluidsynth 2.0.4 /gnu/store/6zpn2p85412dalq7bpfz6sv89pg0hfsp-fluidsynth-2.0.4

^C

So, there I reconnect to Internet and restart guix-daemon with `# herd restart guix-daemon`, and everything goes fine.

I think it is a bug, cause guix-daemon did not delete packages. Some blocks present there when Internet goes down.
[Message part 2 (text/html, inline)]

Information forwarded to bug-guix <at> gnu.org:
bug#35532; Package guix. (Fri, 03 May 2019 09:48:02 GMT) Full text and rfc822 format available.

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

From: Ludovic Courtès <ludo <at> gnu.org>
To: znavko <at> disroot.org
Cc: 35532 <at> debbugs.gnu.org
Subject: Re: bug#35532: guix-daemon was freezed
Date: Fri, 03 May 2019 11:46:50 +0200
Hello,

znavko <at> disroot.org skribis:

> So, there I reconnect to Internet and restart guix-daemon with `# herd restart guix-daemon`, and everything goes fine.

Is this reproducible, or is the problem gone now?

It may have been a transient networking issue, it’s hard to tell.

Thanks,
Ludo’.




Reply sent to Maxim Cournoyer <maxim.cournoyer <at> gmail.com>:
You have taken responsibility. (Tue, 14 Dec 2021 16:53:01 GMT) Full text and rfc822 format available.

Notification sent to znavko <at> disroot.org:
bug acknowledged by developer. (Tue, 14 Dec 2021 16:53:01 GMT) Full text and rfc822 format available.

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

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: znavko <at> disroot.org, 35532-done <at> debbugs.gnu.org
Subject: Re: bug#35532: guix-daemon was freezed
Date: Tue, 14 Dec 2021 11:52:22 -0500
Hello,

Ludovic Courtès <ludo <at> gnu.org> writes:

> Hello,
>
> znavko <at> disroot.org skribis:
>
>> So, there I reconnect to Internet and restart guix-daemon with `# herd restart guix-daemon`, and everything goes fine.
>
> Is this reproducible, or is the problem gone now?
>
> It may have been a transient networking issue, it’s hard to tell.

Closing, 2 years and 32 weeks later without a reply.

Thank you,

Maxim




Information forwarded to bug-guix <at> gnu.org:
bug#35532; Package guix. (Tue, 28 Dec 2021 22:32:01 GMT) Full text and rfc822 format available.

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

From: Tobias Geerinckx-Rice <me <at> tobias.gr>
To: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Cc: Ludovic Courtès <ludo <at> gnu.org>, bug-guix <at> gnu.org,
 35532-done <at> debbugs.gnu.org
Subject: Re: bug#35532: guix-daemon was freezed
Date: Tue, 28 Dec 2021 23:31:25 +0100
[Message part 1 (text/plain, inline)]
Maxim Cournoyer 写道:
> Closing, 2 years and 32 weeks later without a reply.

This might be tracked as <https://issues.guix.gnu.org/52845> now 
(although we'll never know for sure).

Kind regards,

T G-R
[signature.asc (application/pgp-signature, inline)]

Information forwarded to bug-guix <at> gnu.org:
bug#35532; Package guix. (Tue, 28 Dec 2021 22:32:02 GMT) Full text and rfc822 format available.

bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Wed, 26 Jan 2022 12:24:05 GMT) Full text and rfc822 format available.

This bug report was last modified 2 years and 85 days ago.

Previous Next


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