6:18 p.m.
Will be located at mirror.colorado.edu, only EPEL is planned for now.
We are located in the US, IP address is 128.138.184.3, 1g link speed,
will be contacting a tier 1 mirror, though honestly we might be a good
candidate for that as well.
-Erinn
11:15 a.m.
On Tue, Feb 20, 2018 at 02:18:38PM -0700, Erinn Looney-Triggs wrote:
Will be located at mirror.colorado.edu, only EPEL is planned for
now.
We are located in the US, IP address is 128.138.184.3, 1g link speed,
will be contacting a tier 1 mirror, though honestly we might be a good
candidate for that as well.
Your mirrormanager entry almost looks correct. The only problem is that
our crawler cannot connect to your mirror. In fact, I have problems
connecting to your mirror from multiple locations, with multiple
different errors:
$ curl https://mirror.colorado.edu/fedora/epel/ -v
either this:
* OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to mirror.colorado.edu:443
* stopped the pause stream!
* Closing connection 0
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to mirror.colorado.edu:443
or:
* About to connect() to mirror.colorado.edu port 443 (#0)
* Trying 128.138.184.3... Connection timed out
* couldn't connect to host
* Closing connection #0
curl: (7) couldn't connect to host
or:
* About to connect() to mirror.colorado.edu port 443 (#0)
* Trying 128.138.184.3...
* Connected to mirror.colorado.edu (128.138.184.3) port 443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
* NSS error -5961 (PR_CONNECT_RESET_ERROR)
* TCP connection reset by peer
* Closing connection 0
curl: (35) TCP connection reset by peer
So all kind of different errors, which make it impossible for our crawler to
connect to your mirror.
I would also be great if you could offer rsync access as that makes the
crawler so much more efficient.
Adrian
1:19 p.m.
Yeah, seems to be because everyone's Cron jobs fire at the top of the hour and the
site gets overwhelmed. You run the same thing now, it'll work. We'll be adjusting
resources to get things working.
________________________________
From: Adrian Reber <adrian(a)lisas.de>
Sent: Friday, February 23, 2018 7:15:17 AM
To: Erinn D Looney-Triggs
Cc: mirror-admin(a)lists.fedoraproject.org
Subject: Re: New public mirror in the works
On Tue, Feb 20, 2018 at 02:18:38PM -0700, Erinn Looney-Triggs wrote:
Will be located at mirror.colorado.edu, only EPEL is planned for
now.
We are located in the US, IP address is 128.138.184.3, 1g link speed,
will be contacting a tier 1 mirror, though honestly we might be a good
candidate for that as well.
Your mirrormanager entry almost looks correct. The only problem is that
our crawler cannot connect to your mirror. In fact, I have problems
connecting to your mirror from multiple locations, with multiple
different errors:
$ curl https://mirror.colorado.edu/fedora/epel/ -v
either this:
* OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to mirror.colorado.edu:443
* stopped the pause stream!
* Closing connection 0
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to
mirror.colorado.edu:443
or:
* About to connect() to mirror.colorado.edu port 443 (#0)
* Trying 128.138.184.3... Connection timed out
* couldn't connect to host
* Closing connection #0
curl: (7) couldn't connect to host
or:
* About to connect() to mirror.colorado.edu port 443 (#0)
* Trying 128.138.184.3...
* Connected to mirror.colorado.edu (128.138.184.3) port 443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
* NSS error -5961 (PR_CONNECT_RESET_ERROR)
* TCP connection reset by peer
* Closing connection 0
curl: (35) TCP connection reset by peer
So all kind of different errors, which make it impossible for our crawler to
connect to your mirror.
I would also be great if you could offer rsync access as that makes the
crawler so much more efficient.
Adrian
1:47 p.m.
On Fri, Feb 23, 2018 at 04:19:54PM +0000, Erinn D Looney-Triggs wrote:
Yeah, seems to be because everyone's Cron jobs fire at the top of
the hour and the site gets overwhelmed. You run the same thing now, it'll work.
We'll be adjusting resources to get things working.
Sounds good. Our crawler still cannot reach your mirror:
send: u'HEAD /fedora/epel/ HTTP/1.1\r\nHost: mirror.colorado.edu\r\nAccept-Encoding:
identity\r\nConnection: Keep-Alive\r\nPragma: no-cache\r\nUser-Agent:
mirrormanager-crawler/0.1 (+https://github.com/fedora-infra/mirrormanager2/)\r\n\r\n'
reply: 'HTTP/1.1 404 Not Found\r\n'
header: Date: Fri, 23 Feb 2018 16:33:38 GMT
header: Server: Apache/2.4.6 (Red Hat Enterprise Linux) OpenSSL/1.0.2k-fips
header: Strict-Transport-Security: max-age=15768000
header: Keep-Alive: timeout=5, max=100
header: Connection: Keep-Alive
header: Content-Type: text/html; charset=iso-8859-1
Our crawler still tries to access your mirror via http with a HEAD
request, to see if a basic connectivity is there. You have redirect
to https, but that does only work for GET requests.
To test: curl http://mirror.colorado.edu/fedora/epel/ -vI
Gives me a 404
Adrian
1:59 p.m.
Hmm, well honestly in this day and age, with everything moving to https
I considered just disabling port 80 access altogether. But I'll look
into what I need to do to get your request working.
-Erinn
On 02/23/2018 09:47 AM, Adrian Reber wrote:
On Fri, Feb 23, 2018 at 04:19:54PM +0000, Erinn D Looney-Triggs
wrote:
> Yeah, seems to be because everyone's Cron jobs fire at the top of the hour and
the site gets overwhelmed. You run the same thing now, it'll work. We'll be
adjusting resources to get things working.
Sounds good. Our crawler still cannot reach your mirror:
send: u'HEAD /fedora/epel/ HTTP/1.1\r\nHost: mirror.colorado.edu\r\nAccept-Encoding:
identity\r\nConnection: Keep-Alive\r\nPragma: no-cache\r\nUser-Agent:
mirrormanager-crawler/0.1 (+https://github.com/fedora-infra/mirrormanager2/)\r\n\r\n'
reply: 'HTTP/1.1 404 Not Found\r\n'
header: Date: Fri, 23 Feb 2018 16:33:38 GMT
header: Server: Apache/2.4.6 (Red Hat Enterprise Linux) OpenSSL/1.0.2k-fips
header: Strict-Transport-Security: max-age=15768000
header: Keep-Alive: timeout=5, max=100
header: Connection: Keep-Alive
header: Content-Type: text/html; charset=iso-8859-1
Our crawler still tries to access your mirror via http with a HEAD
request, to see if a basic connectivity is there. You have redirect
to https, but that does only work for GET requests.
To test: curl http://mirror.colorado.edu/fedora/epel/ -vI
Gives me a 404
Adrian
_______________________________________________
Mirror-admin mailing list -- mirror-admin(a)lists.fedoraproject.org
To unsubscribe send an email to mirror-admin-leave(a)lists.fedoraproject.org
2263
days inactive
2266
days old
mirror-admin@lists.fedoraproject.org
4 comments
4 participants
participants (4)
-
Adrian Reber -
Erinn D Looney-Triggs -
Erinn Looney-Triggs -
Erinn Looney-Triggs