all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Ahmad Draidi <ar2000jp@gmail.com>
Cc: 53998@debbugs.gnu.org
Subject: bug#53998: Guix pull always gets stuck at ~80% on fresh i686 1.3.0 install
Date: Tue, 15 Feb 2022 13:56:15 -0500	[thread overview]
Message-ID: <Ygv3T4zjoEymMAig@jasmine.lan> (raw)
In-Reply-To: <CANS4MAiLFvRbF7iYQkH_n6x5nHd7fZ9s2dRtQ-ATYYoGq==YSQ@mail.gmail.com>

On Mon, Feb 14, 2022 at 04:16:09PM +0000, Ahmad Draidi wrote:
> Running 'guix pull' on a fresh basic install of Guix System 1.3.0 for i686
> gets stuck at around 80%.

Okay, can you share the result of `guix describe` to confirm what
revision of Guix you're using?

Can you use strace to see what it's doing when it's stuck?

For example, you can `guix install strace` as root, and then run this
(again, as root):

`strace -f /proc/$(pgrep guix-daemon)/exe | tee log`

You might compress the resulting log before emailing it:

`xz log`

> I tested this on a Pentium 4 32bits laptop with 786MB RAM at first, and
> then switched to a VM with 8 GBs RAM, 2+ cores, 60GBs SSD to avoid any
> resources issues.

786MB RAM is definitely not enough to use Guix currently, sorry. But 8GB
RAM is more than enough. We do want to reduce the resource requirements
but it's not a priority, since most people have at least 2GB. Help
wanted!

> Terminal log of one of the runs and config.scm attached.

The log seems to contain a lot of extraneous information. Is the problem
that it stops making progress while building
'/gnu/store/00bgnqkqyf0k865gx4ps9fliysidxz61-guix-packages-base.drv'?




  reply	other threads:[~2022-02-15 18:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-14 16:16 bug#53998: Guix pull always gets stuck at ~80% on fresh i686 1.3.0 install Ahmad Draidi
2022-02-15 18:56 ` Leo Famulari [this message]
2022-02-16 14:58   ` Ludovic Courtès
2022-02-23 15:17     ` Ahmad Draidi
2022-02-27 13:20       ` Ahmad Draidi
2022-02-27 21:41         ` Ludovic Courtès
2022-03-01  8:33           ` Ahmad Draidi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Ygv3T4zjoEymMAig@jasmine.lan \
    --to=leo@famulari.name \
    --cc=53998@debbugs.gnu.org \
    --cc=ar2000jp@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.