EPEL Repo Problem
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.
8 thoughts on - EPEL Repo Problem
Am Mittwoch, 30. Januar 2019, 06:24:46 CET schrieb SternData:
I have 100…. from this Mails I mean the Mirrors are broken :-( ??
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).
–Since I’m seeing the same errors intermittently, I tried to run the script. Recall that CentOS still ships with Python 2. First I had to install rh-python36 from SCL. Then I had to change the script’s shebang to
“#!/usr/bin/env python”. Now it complains that there’s no requests module. I don’t know how to resolve Python3 dependencies for a python installed from SCL. How far down the rabbit hole will I need to go to get the script working? ;)
[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
[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]$
Yeah.. sorry. I didn’t see I had made this one little change to my version:
diff –git a/check_metalink b/check_metalink index f2beeb5..380b16d 100755
— a/check_metalink
+++ b/check_metalink
@@ -1,4 +1,4 @@
-#!/bin/python3
+#!/bin/python
I will see if I can make this work without that pathc.
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.
Hello,
my test have this
./check_metalink –repo epel –check-master
Testing repo=epel, arch=i386
Metalink provided by: proxy02.fedoraproject.org
Server date: Thu, 31 Jan 2019 14:05:26 GMT
Repo epel, arch i386 errored: list index out of range Testing repo=epel, arch=x86_64
Metalink provided by: proxy02.fedoraproject.org
Server date: Thu, 31 Jan 2019 14:05:27 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
m Mittwoch, 30. Januar 2019, 16:58:58 CET schrieb Stephen John Smoogen:
Argh I missed the problem until now.
./check_metalink –repo=epel-6 –check-master
[will test i386 and x86_64]
./check_metalink –repo=epel-7 –check-master
[will test just x86_64]
./check_metalink –repo=epel
[does not error out like it shoudl.]
—
Stephen J Smoogen.