Guix pull always gets stuck at ~80% on fresh i686 1.3.0 install

  • Open
  • quality assurance status badge
Details
3 participants
  • Ahmad Draidi
  • Leo Famulari
  • Ludovic Courtès
Owner
unassigned
Submitted by
Ahmad Draidi
Severity
normal
A
A
Ahmad Draidi wrote on 14 Feb 2022 17:16
(address . bug-guix@gnu.org)
CANS4MAiLFvRbF7iYQkH_n6x5nHd7fZ9s2dRtQ-ATYYoGq==YSQ@mail.gmail.com
Hello Guix hackers,

Running 'guix pull' on a fresh basic install of Guix System 1.3.0 for i686
gets stuck at around 80%.
I've tested this several times and it happens most of the time. In the
other rare few cases other errors showed up. Not a single 'pull' succeeded
either way.
I let the pull run for days sometimes but it never finishes.
I run Guix x86_64 on my other systems without issues in the same
environment.

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.
Terminal log of one of the runs and config.scm attached.

Let me know if there's anything I can help with.

Regards,
Ahmad
Attachment: file
;; This is an operating system configuration generated ;; by the graphical installer. (use-modules (gnu)) (use-service-modules desktop networking ssh xorg) (operating-system (locale "en_US.utf8") (timezone "Africa/Freetown") (keyboard-layout (keyboard-layout "us")) (host-name "Guix8601") (users (cons* (user-account (name "user") (comment "User") (group "users") (home-directory "/home/user") (supplementary-groups '("wheel" "netdev" "audio" "video"))) %base-user-accounts)) (packages (append (list (specification->package "nss-certs")) %base-packages)) (services (append (list (service openssh-service-type) (service dhcp-client-service-type)) %base-services)) (bootloader (bootloader-configuration (bootloader grub-bootloader) (target "/dev/sda") (keyboard-layout keyboard-layout))) (swap-devices (list (uuid "573b665f-259d-46fa-a26b-ca6c9b65865e"))) (file-systems (cons* (file-system (mount-point "/") (device (uuid "8eb36ef8-95d9-4dac-a82c-398995638ae6" 'ext4)) (type "ext4")) %base-file-systems)))
Attachment: run3-sess1.log
L
L
Leo Famulari wrote on 15 Feb 2022 19:56
(name . Ahmad Draidi)(address . ar2000jp@gmail.com)(address . 53998@debbugs.gnu.org)
Ygv3T4zjoEymMAig@jasmine.lan
On Mon, Feb 14, 2022 at 04:16:09PM +0000, Ahmad Draidi wrote:
Toggle quote (3 lines)
> 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`

Toggle quote (4 lines)
> 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!

Toggle quote (2 lines)
> 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'?
L
L
Ludovic Courtès wrote on 16 Feb 2022 15:58
(name . Leo Famulari)(address . leo@famulari.name)
87ee42x3hk.fsf@gnu.org
Hi,

Leo Famulari <leo@famulari.name> skribis:

Toggle quote (7 lines)
> 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?

Also, there were improvements in this area a few days ago:


Could you maybe try again, Ahmad, and let us know how it goes?

Thanks,
Ludo’.
A
A
Ahmad Draidi wrote on 23 Feb 2022 16:17
(name . Ludovic Courtès)(address . ludo@gnu.org)
CANS4MAh-pZcPHsUAC6VE+ip=LdyB_RfR4PaBTRzqB==5XcxQxA@mail.gmail.com
Hello Leo and Ludo,

Sorry for the late reply.

On Wed, Feb 16, 2022 at 2:58 PM Ludovic Courtès <ludo@gnu.org> wrote:
Toggle quote (6 lines)
> Also, there were improvements in this area a few days ago:
>
> https://issues.guix.gnu.org/53506
>
> Could you maybe try again, Ahmad, and let us know how it goes?

I tested again using the same method (clean install, same VM, etc) but
with strace running this time a couple of days ago and it failed, but
just now it passed.
I'll test a couple of times again and let you know.

Regards,
Ahmad
A
A
Ahmad Draidi wrote on 27 Feb 2022 14:20
(address . 53998@debbugs.gnu.org)
417d2ede-f783-1fff-76de-11a24e56c617@gmail.com
Hello again,

On 2/23/22 19:17, Ahmad Draidi wrote:
Toggle quote (5 lines)
> I tested again using the same method (clean install, same VM, etc) but
> with strace running this time a couple of days ago and it failed, but
> just now it passed.
> I'll test a couple of times again and let you know.

I tested a few more times using the same method (clean install, etc) and
the results were like this:

- Pull seg faulted, 2nd pull worked

- Pull seg faulted, 2nd pull got stuck

- Pull finished without issues

- Pull finished without issues

- Pull seg faulted, 2nd pull worked

- Pull finished without issues

- Pull seg faulted (log attached), 2nd pull worked, system reconfigure
worked, reboot then pull again worked


It's a bit random now, but at least it passes sometimes.

Log file attached for the last attempt.


Let me know if there's anything I can help with.


Regards,

Ahmad
Attachment: file
L
L
Ludovic Courtès wrote on 27 Feb 2022 22:41
(name . Ahmad Draidi)(address . ar2000jp@gmail.com)
87fso4t2ak.fsf@gnu.org
Hi Ahmad,

Ahmad Draidi <ar2000jp@gmail.com> skribis:

Toggle quote (21 lines)
> I tested a few more times using the same method (clean install, etc)
> and the results were like this:
>
> - Pull seg faulted, 2nd pull worked
>
> - Pull seg faulted, 2nd pull got stuck
>
> - Pull finished without issues
>
> - Pull finished without issues
>
> - Pull seg faulted, 2nd pull worked
>
> - Pull finished without issues
>
> - Pull seg faulted (log attached), 2nd pull worked, system reconfigure
> worked, reboot then pull again worked
>
>
> It's a bit random now, but at least it passes sometimes.

That doesn’t sound great.

How much (v)RAM does this (virtual) machine have?

Thanks for testing and reporting back,
Ludo’.
A
A
Ahmad Draidi wrote on 1 Mar 2022 09:33
(name . Ludovic Courtès)(address . ludo@gnu.org)
c609e6d9-db3c-bb43-a8d7-2b3b56decc2f@gmail.com
Hi Ludo,


On 2/28/22 01:41, Ludovic Courtès wrote:
Toggle quote (2 lines)
> That doesn’t sound great.
> How much (v)RAM does this (virtual) machine have?
user@Guix8601 ~$ free -mt
             total        used        free      shared  buff/cache
  available
Mem:           8026         104        7818           0         104
       7393
Swap:          3071           0        3071
Total:        11098         104       10890


Thanks,

Ahmad
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 53998@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 53998
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch