search for: sugaree

...t 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):...

...iterwijk/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...

...t; >> > > 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 err...

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