unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: raingloom <raingloom@riseup.net>
To: "Wamm K. D." <jaft.r@outlook.com>
Cc: help-guix@gnu.org
Subject: Re: Guix Halts After "updating substitutes from …"
Date: Wed, 25 May 2022 01:22:31 +0200	[thread overview]
Message-ID: <20220525012231.4821654d@riseup.net> (raw)
In-Reply-To: <BY5PR07MB7029A609913B267A5DE93FDD99D79@BY5PR07MB7029.namprd07.prod.outlook.com>

On Tue, 24 May 2022 17:55:20 -0500
"Wamm K. D." <jaft.r@outlook.com> wrote:

> Hey, hey; 'not sure what caused this but my ~guix~ command suddenly
> started getting stuck, when I do a pull or try to install a package,
> after
> 
> > substitute: updating substitutes from 'https://ci.guix.gnu.org'...
> > 100.0%  
> 
> I haven't let it run for longer than an hour but it just sits there
> and doesn't progress any further. When I run ~guix upgrade~, it halts,
> similarly, after listing which programs it's going to upgrade.
> 
> Anyone, possibly, know what this is (or, at least, how I might get
> around it)?
> 
> Thanks for any help!
> 

For some quick diagnostics maybe you could try running it with strace,
or attaching strace to the running process to see if it's stuck on a
system call or if it's some kind of deadlock or livelock or other
concurrency related fun.
Actually... I thiiink I've experienced a hang like this on my i686
machine, but aborting it and running pull again fixed it.
Does it happen always?


  parent reply	other threads:[~2022-05-24 23:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-24 22:55 Guix Halts After "updating substitutes from …" Wamm K. D.
2022-05-24 23:19 ` Tobias Geerinckx-Rice
2022-05-24 23:50   ` Wamm K. D.
2022-05-25  8:39   ` Wil deBeest
2022-05-24 23:22 ` raingloom [this message]
2022-05-25  0:10   ` Wamm K. D.

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=20220525012231.4821654d@riseup.net \
    --to=raingloom@riseup.net \
    --cc=help-guix@gnu.org \
    --cc=jaft.r@outlook.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).