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. -- -- Steve
Am Mittwoch, 30. Januar 2019, 06:24:46 CET schrieb SternData:> 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.I have 100.... from this Mails I mean the Mirrors are broken :-( ?? -- mit freundliche Gr??en / best regards, G?nther J. Niederwimmer
On Wed, 30 Jan 2019 at 00:25, SternData <subscribed-lists at 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).> > -- > -- Steve > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos >-- Stephen J Smoogen.
--On Wednesday, January 30, 2019 6:57 AM -0500 Stephen John Smoogen <smooge at gmail.com> wrote:> 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? ;)
On 1/30/19 5:57 AM, Stephen John Smoogen wrote:> On Wed, 30 Jan 2019 at 00:25, SternData <subscribed-lists at 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 at 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 at 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 at sugaree check_metalink]$> >-- -- Steve
On Wed, 30 Jan 2019 at 09:21, Kenneth Porter <shiva at sewingwitch.com> wrote:> --On Wednesday, January 30, 2019 6:57 AM -0500 Stephen John Smoogen > <smooge at gmail.com> wrote: > > > 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? ;) > >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.> _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos >-- Stephen J Smoogen.