On Wed, 30 Jan 2019 at 09:45, SternData subscribed-lists@sterndata.com wrote:
On 1/30/19 5:57 AM, Stephen John Smoogen wrote:
On Wed, 30 Jan 2019 at 00:25, SternData subscribed-lists@sterndata.com wrote:
This keeps logging:
Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64
error
was 14: HTTPS Error 503 - Service Unavailable
I've removed the epel-release package, done a "yum clean all", then reinstalled it, but still get the same error.
Can you run the code from: https://github.com/puiterwijk/check_metalink
to
see if we can pin down the proxy which is the problem (there are 14 and
our
checks are showing they are ok so I need to pin this down somewhere).
[sdstern@sugaree check_metalink]$ ./check_metalink --repo epel --check-mirrors Client IP: 2604:a880:800:a1::6ab:c001
Testing repo=epel, arch=x86_64 Metalink provided by: proxy11.fedoraproject.org Server date: Wed, 30 Jan 2019 14:43:18 GMT Repo epel, arch x86_64 errored: list index out of range OK metalinks (0): Bad metalinks (0): Exception metalinks (1): epel.x86_64 OK metalink means that at least one mirror is valid
OK it looks like the server we have this proxy on is swamped and is causing problems. I am trying to see what we can do to fix that.
There is no official epel.i386 so the second one errors for that reason.
[sdstern@sugaree check_metalink]$ ./check_metalink --repo epel --check-master Client IP: 2604:a880:800:a1::6ab:c001
Testing repo=epel, arch=i386 Metalink provided by: proxy11.fedoraproject.org Server date: Wed, 30 Jan 2019 14:43:45 GMT Repo epel, arch i386 errored: list index out of range Testing repo=epel, arch=x86_64 Metalink provided by: proxy11.fedoraproject.org Server date: Wed, 30 Jan 2019 14:43:45 GMT Repo epel, arch x86_64 errored: list index out of range OK metalinks (0): Bad metalinks (0): Exception metalinks (2): epel.i386, epel.x86_64 [sdstern@sugaree check_metalink]$
-- -- Steve