From: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
To: Attila Lendvai <attila@lendvai.name>
Cc: guix-devel@gnu.org
Subject: Re: Errors with inconsistent network, bad gateway (nginx) and others
Date: Fri, 15 Nov 2024 23:18:58 +0000 [thread overview]
Message-ID: <8b75bfe5-ee48-49b3-8e4a-964f7e30a76a@posteo.de> (raw)
In-Reply-To: <43934c92-00e0-4c77-888c-2ea4b6dc10b8@posteo.de>
[-- Attachment #1: Type: text/plain, Size: 1945 bytes --]
On 14.11.24 00:53, Zelphir Kaltstahl wrote:
> On 13.11.24 23:30, Attila Lendvai wrote:
>>> 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
>> when you see this error then just retry. i often need to restart operations 3-5 times due to this error to finally run through.
>>
>> this is a known issue, and IIRC it has even been addressed recently to some extent. you may be pulling in the neccessary change right now that will make it behave better.
>>
>> i suspect your first error was also network/service related (the 502 "Bad Gateway" suggests that the lisp process behind nginx was not available at that moment; e.g. it was restarting).
>
> Hm now I seem to also have issues upgrading Guix itself. Still network
> related, I think:
>
> ~~~~ guix substitute: warning: while fetching
> https://ci.guix.gnu.org/nar/lzip/xg7hlcfd0fn33h48h7qkmpk4b0phzsfd-guix-cli:
> server is somewhat slow guix substitute: warning: try `--no-substitutes' if
> the problem persists guix substitute: warning: bordeaux.guix.gnu.org: host not
> found: Temporary failure in name resolution guix substitute: error: failed to
> find alternative substitute for
> '/gnu/store/xg7hlcfd0fn33h48h7qkmpk4b0phzsfd-guix-cli' substitution of
> /gnu/store/xg7hlcfd0fn33h48h7qkmpk4b0phzsfd-guix-cli failed guix pull: error:
> corrupt input while restoring archive from #<closed: file 7f8de82423f0> ~~~~
>
> OK, I will try another day.
>
> --
> repositories:https://notabug.org/ZelphirKaltstahl,https://codeberg.org/ZelphirKaltstahl
Just wanted to report back: I tried again. Today all worked smoothly.
Best regards,
Zelphir
--
repositories:https://notabug.org/ZelphirKaltstahl,https://codeberg.org/ZelphirKaltstahl
[-- Attachment #2: Type: text/html, Size: 3614 bytes --]
next prev parent reply other threads:[~2024-11-15 23:19 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 [this message]
2024-11-14 11:08 ` Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8b75bfe5-ee48-49b3-8e4a-964f7e30a76a@posteo.de \
--to=zelphirkaltstahl@posteo.de \
--cc=attila@lendvai.name \
--cc=guix-devel@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 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.