Mirror-admin October 2017

mirror-admin@lists.fedoraproject.org

3 participants
2 discussions

EPEL restructuring causing mass download
by Chris Schanzle 06 Nov '17

06 Nov '17

Looks like the EPEL 6 and 7 repos transitioned from a flat layout of packages to the Packages/[A-z]/ layout. Would have been nice to use hardlinks to transition. Tough on the main mirrors and all their clients to unnecessarily re-download 150+ GB in one day...

2 1

Fedora mirror mirrors.liquidweb.com
by Adrian Reber 10 Oct '17

10 Oct '17

Hello mirrors.liquidweb.com admins, Fedora's mirror crawler has trouble crawling your mirror as it does return a unusual status code: # curl http://mirrors.liquidweb.com/fedora-epel/ -v * About to connect() to mirrors.liquidweb.com port 80 (#0) * Trying 69.167.187.144... * Connected to mirrors.liquidweb.com (69.167.187.144) port 80 (#0) > GET /fedora-epel/ HTTP/1.1 > User-Agent: curl/7.29.0 > Host: mirrors.liquidweb.com > Accept: */* > < HTTP/1.1 000 < Server: nginx < Date: Mon, 09 Oct 2017 12:37:13 GMT < Content-Type: text/html < Transfer-Encoding: chunked < Connection: keep-alive The crawler expects the status code 200 if everything works correctly and ignores your mirror because of the status code 000. Any reason for status code 000. It seems that the code 000 is something Akamai uses for requests where the client aborted: """ Log Delivery Services (LDS) LDS will show a 000 for any 200 or 206 responses with a client abort: the object was served correctly from the origin or edge, but the end-user terminated the connection/transaction before it completed. """ Not sure if that is related to your situation. But right now your mirror is disabled as it seems to be inaccessible (at least from the crawlers point of view). Adrian

2 5

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

Mirror-admin October 2017