From: Simon Tournier <zimon.toutoune@gmail.com>
To: 63666@debbugs.gnu.org
Cc: ludo@gnu.org
Subject: bug#63666: sporadic “guix substitute: error: connect*: Connection timed out”
Date: Tue, 23 May 2023 17:14:50 +0200 [thread overview]
Message-ID: <861qj7uljp.fsf@gmail.com> (raw)
Hi,
On different machines (laptop, desktop, workstation) using different
networks, running different revisions of Guix, I often see this sort of
message (here bash-static and aspell-dict-fr are examples, I see that
for various others):
--8<---------------cut here---------------start------------->8---
bash-static-5.1.16 701KiB 409KiB/s 00:00 ▕█▋ ▏ 9.1%guix substitute: warning: while fetching https://ci.guix.gnu.org/nar/lzip/s3lfskbxkq65f4zf0iair8yz3s7nskml-aspell-dict-fr-0.50-3: server is somewhat slow
guix substitute: warning: try `--no-substitutes' if the problem persists
guix substitute: error: connect*: Connection timed out
--8<---------------cut here---------------end--------------->8---
And I have not noticed if it’s always about the same compression (lzip).
The most recent failure uses 3f59fd6 (pulled on May 23) with:
$ /root/.config/guix/current/bin/guix-daemon --version
guix-daemon (GNU Guix) 1.3.0-31.3170843
Well, if that’s because guix-daemon is too old, maybe we could provide a
more meaningful message.
Sometimes, I even get:
--8<---------------cut here---------------start------------->8---
substitute: updating substitutes from 'https://ci.guix.gnu.org'... 0.0%guix substitute: warning: ci.guix.gnu.org: connection failed: Connection timed out
--8<---------------cut here---------------end--------------->8---
Cheers,
simon
next reply other threads:[~2023-05-23 15:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 15:14 Simon Tournier [this message]
2023-05-23 16:16 ` bug#63666: sporadic “guix substitute: error: connect*: Connection timed out” Simon Tournier
2023-05-24 15:01 ` Ludovic Courtès
2023-05-25 13:36 ` Simon Tournier
2023-05-26 16:47 ` Ludovic Courtès
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=861qj7uljp.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=63666@debbugs.gnu.org \
--cc=ludo@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).