Displaying 4 results from an estimated 4 matches for "proxy11".
Did you mean:
proxy01
2019 Jan 30
2
EPEL repo problem
...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...
2019 Jan 31
1
EPEL repo problem
...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 lea...
2019 Jan 30
0
EPEL repo problem
...gt; > 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
>
>
OK it lo...
2019 Jan 30
5
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.
--
-- Steve