From: "Ludovic Courtès" <ludo@gnu.org>
To: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
Cc: guix-devel@gnu.org
Subject: Re: Errors with inconsistent network, bad gateway (nginx) and others
Date: Thu, 14 Nov 2024 12:08:55 +0100 [thread overview]
Message-ID: <874j4aoywo.fsf@gnu.org> (raw)
In-Reply-To: <5565923c-493b-43c7-8d1d-3127d462741e@posteo.de> (Zelphir Kaltstahl's message of "Wed, 13 Nov 2024 22:17:28 +0000")
Hi,
Zelphir Kaltstahl <zelphirkaltstahl@posteo.de> skribis:
> Then I did `guix package -u` to update installed packages. However, I
> ran into an error:
[...]
> In guix/scripts/substitute.scm:
> 467:7 8 (download-nar #<<narinfo> path: "/gnu/store/bqk5b108p6…> …)
> In ice-9/boot-9.scm:
> 1747:15 7 (with-exception-handler #<procedure 7f3fc999ede0 at ic…> …)
> 1685:16 6 (raise-exception _ #:continuable? _)
> 1683:16 5 (raise-exception _ #:continuable? _)
> 1685:16 4 (raise-exception _ #:continuable? _)
> 1780:13 3 (_ #<&compound-exception components: (#<&error> #<&irri…>)
> 1685:16 2 (raise-exception _ #:continuable? _)
> 1683:16 1 (raise-exception _ #:continuable? _)
> 1685:16 0 (raise-exception _ #:continuable? _)
>
> ice-9/boot-9.scm:1685:16: In procedure raise-exception:
> ERROR:
> 1. &http-get-error:
> uri: #<<uri> scheme: https userinfo: #f host: "ci.guix.gnu.org" port: #f path: "/nar/lzip/bqk5b108p6wxd5iwmn080zjcfav48wmr-libxext-1.3.4" query: #f fragment: #f>
> code: 502
> reason: "Bad Gateway"
> headers: ((server . "nginx") (date . #<date nanosecond: 0 second: 26 minute: 14 hour: 19 day: 13 month: 11 year: 2024 zone-offset: 0>) (content-type text/html) (content-length . 150) (connection keep-alive))
> 2. &message:"https://ci.guix.gnu.org/nar/lzip/bqk5b108p6wxd5iwmn080zjcfav48wmr-libxext-1.3.4:
> HTTP download failed: 502 (\"Bad Gateway\")"
> substitution of /gnu/store/bqk5b108p6wxd5iwmn080zjcfav48wmr-libxext-1.3.4 failed
> guix package: error: corrupt input while restoring archive from socket
I believe this particular error was addressed in
ddc9d66f2b00f62eb35c3da819dc684ec4a50227 back in March.
If you upgrade to a more recent ‘guix-daemon’, it should be gone:
https://guix.gnu.org/manual/devel/en/html_node/Upgrading-Guix.html
Before upgrading, could you run ‘pgrep -fa guix-daemon’ or similar to
see which version is running?
> python-3.10.7-idle 692KiB 799KiB/s 00:01 ▕██████████████████▏ 100.0%
> python-3.10.7-tk 25KiB 1.4MiB/s 00:00 ▕██████████████████▏ 100.0%
> substitute: updating substitutes from 'https://ci.guix.gnu.org'... 100.0%
> substitute: updating substitutes from 'https://bordeaux.guix.gnu.org'... 0.0%guix substitute: error: TLS error in procedure 'read_from_session_record_port': Error in the pull function.
> guix package: error: `/gnu/store/vkyprwq3g00ki69ahby3mhdxa65hnzgy-guix-command substitute' died unexpectedly
This was fixed more recently in commit
fa70c141552c76cf4dc9666f577bf6b471fa0d50. Again, upgrading
‘guix-daemon’ should help.
HTH!
Ludo’.
next prev parent reply other threads:[~2024-11-14 11:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 22:17 Errors with inconsistent network, bad gateway (nginx) and others Zelphir Kaltstahl
2024-11-13 22:30 ` Attila Lendvai
[not found] ` <43934c92-00e0-4c77-888c-2ea4b6dc10b8@posteo.de>
2024-11-15 23:18 ` Zelphir Kaltstahl
2024-11-14 11:08 ` Ludovic Courtès [this message]
2024-11-17 0:28 ` Zelphir Kaltstahl
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=874j4aoywo.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=zelphirkaltstahl@posteo.de \
/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).