all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel@gnu.org
Subject: Re: Guix publish pipe error from #{read pipe}# - what nginx.conf to use?
Date: Wed, 17 May 2017 09:10:40 +0200	[thread overview]
Message-ID: <20170517071039.GA15277@thebird.nl> (raw)
In-Reply-To: <20170516062917.GA7072@thebird.nl>

On Tue, May 16, 2017 at 08:29:17AM +0200, Pjotr Prins wrote:
> On a recent guix-publish server I get many of these
> 
>   gzip: stdin: invalid compressed data--format violated
>     r-annotationdbi-1.36.0
>     1.7MiB/s 00:02 | 3.0MiB transferredguix substitute: error: corrupt
>   input while restoring
>     '/gnu/store/g33ns71m61zs5sn758smmc4lnv6h4c4q-r-annotationdbi-1.36.0/site-library/AnnotationDbi/extdata/HG-U95Av2_probe_tab.gz' from #{read pipe}#
> 
> I don't think this is a guix problem per se. I have a hunch the people
> changed the firewall which may cause this.  Anyone any other ideas?

It is an nginx thing. When I go around nginx guix publish works as
expected. Anyone have an example nginx.conf file for guix publish?
Funny thing is that it used to be fine. I think parallel downloads
is messing it up now.

Now we are doing parallel downloads, would it be an idea to do a round
robin on substitute-urls too? Make it optional. May speed downloads up
nicely.

Pj.
-- 

  parent reply	other threads:[~2017-05-17  7:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-16  6:29 Guix publish pipe error from #{read pipe}# Pjotr Prins
2017-05-16  6:57 ` Andy Wingo
2017-05-17  7:10 ` Pjotr Prins [this message]
2017-05-17 12:48   ` Guix publish pipe error from #{read pipe}# - what nginx.conf to use? 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

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

  git send-email \
    --in-reply-to=20170517071039.GA15277@thebird.nl \
    --to=pjotr.public12@thebird.nl \
    --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.