unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Bonface Munyoki K. <me@bonfacemunyoki.com>
To: help-guix@gnu.org
Subject: Re: error: corrupt input while restoring archive from socket
Date: Tue, 16 Mar 2021 21:16:46 +0300	[thread overview]
Message-ID: <86sg4vt14h.fsf@bonfacemunyoki.com> (raw)
In-Reply-To: <YEosI5jO4spytQj8@bluewin.ch> (fulbert@bluewin.ch's message of "Thu, 11 Mar 2021 15:41:39 +0100")

[-- Attachment #1: Type: text/plain, Size: 2941 bytes --]

Hi o/

Fulbert <fulbert@bluewin.ch> writes:

> Le Thu, Mar 11, 2021 at 04:59:42PM +0300, Mikhail Kryshen a écrit :
>> Fulbert <fulbert@bluewin.ch> writes:
>> 
>> > Hello Guixers,
>> >
>> > For the past few days… maybe a couple of weeks (not sure when
>> > it started exactly), I have had frequent errors with
>> > substitutions. Those errors are not [always] reproducible as
>> > another [or more] installation attempt succeed on the same [set of]
>> > file[s].
>> >

I have this same problem :(

[...]

>> I'm seeing this too, but only when guix tries to download from my own
>> local substitute server, which runs current guix-publish exposed
>> directly to the network without reverse proxy.  Downloading from
>> ci.guix.gnu.org works without errors.  Could this be a race condition
>> related to download rate?
>
> Hello and thanks for your time Mikhail,
>
> I only have a local channel with a couple of local files but no
> subtitute server. All downloads go through ci.gui.gnu.org.
>
I ran:

--8<---------------cut here---------------start------------->8---
guix pull --substitute-urls=https://ci.guix.gnu.org
--8<---------------cut here---------------end--------------->8---

and moreover...



>> Downloading from ci.guix.gnu.org works without errors.  Could
>> this be a race condition related to download rate?
>
... with

--8<---------------cut here---------------start------------->8---
guix pull --fallback
--8<---------------cut here---------------end--------------->8---

I still get the same error.

> I don't know. I'm not even sure what it means and how I could
> check that. Wouldn't this kind of problem be handled on the
> network "layers" ?… Because, as stated, I have not experienced
> other problems besides guix substitutions, whether guix related or
> any other use as a connected "desktop" user.
>
The only solution I've come up with looks like:

--8<---------------cut here---------------start------------->8---
#!/bin/bash

for (( ; ; ))
do
    echo "Press CTRL+C to stop..."
    guix pull 2>&1 | tee /tmp/log.txt
    $(grep failed /tmp/log.txt | cut -d' ' -f3) && \
        if [ 1 ]
        then
	    break
        fi
    echo "Building:"
    echo $(grep failed /tmp/log.txt | cut -d' ' -f3)
    sleep 1
    guix build $(grep failed /tmp/log.txt | cut -d' ' -f3)
done
--8<---------------cut here---------------end--------------->8---

where I basically I keep manually rebuilding the
failed drv again and again subsequently until the
operation finishes. I get the same error during
"upgrades"  and also when installing a package :(

>> 
>> > Any idea ? I have not found any recent similar issue on
>> > issues.guix.gnu.org.

Any luck?

[...]

-- 
Bonface M. K. D4F09EB110177E03C28E2FE1F5BBAE1E0392253F
Humble GNU Emacs User / Bearer of scheme-y parens
Curator: <https://upbookclub.com> / Twitter: @BonfaceKilz

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 865 bytes --]

  parent reply	other threads:[~2021-03-16 20:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-09  7:48 error: corrupt input while restoring archive from socket Fulbert
2021-03-09  7:52 ` divoplade
2021-03-09  9:19   ` Fulbert
2021-03-11 13:59 ` Mikhail Kryshen
2021-03-11 14:41   ` Fulbert
2021-03-11 17:59     ` Mikhail Kryshen
2021-03-16 18:16     ` Bonface Munyoki K. [this message]
2021-03-12  0:08   ` Mikhail Kryshen
2021-03-12 14:56     ` Mikhail Kryshen
2021-03-22 10:17 ` Fulbert

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=86sg4vt14h.fsf@bonfacemunyoki.com \
    --to=me@bonfacemunyoki.com \
    --cc=help-guix@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.
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).