Is anyone else having issues getting to vault.centos.org right now? I'm getting connection timed out on the web page, but I can ping the server: $ ping vault.centos.org PING vault.centos.org (54.186.51.210) 56(84) bytes of data. 64 bytes from ec2-54-186-51-210.us-west-2.compute.amazonaws.com (54.186.51.210): icmp_seq=1 ttl=25 time=67.1 ms 64 bytes from ec2-54-186-51-210.us-west-2.compute.amazonaws.com (54.186.51.210): icmp_seq=2 ttl=25 time=66.6 ms 64 bytes from ec2-54-186-51-210.us-west-2.compute.amazonaws.com (54.186.51.210): icmp_seq=3 ttl=25 time=67.6 ms
Chris
Is anyone else having issues getting to vault.centos.org right now? I'm getting connection timed out on the web page, but I can ping the server: $ ping vault.centos.org PING vault.centos.org (54.186.51.210) 56(84) bytes of data. 64 bytes from ec2-54-186-51-210.us-west-2.compute.amazonaws.com (54.186.51.210): icmp_seq=1 ttl=25 time=67.1 ms 64 bytes from ec2-54-186-51-210.us-west-2.compute.amazonaws.com (54.186.51.210): icmp_seq=2 ttl=25 time=66.6 ms 64 bytes from ec2-54-186-51-210.us-west-2.compute.amazonaws.com (54.186.51.210): icmp_seq=3 ttl=25 time=67.6 ms
Yes, also mostly down for me. Some requests were answered but unable to really use the site.
Simon
On 2/28/22 23:46, Simon Matter wrote:
Yes, also mostly down for me. Some requests were answered but unable to really use the site.
Is it just overloaded? I've seen a few examples recently of people building CentOS 8 containers by building repo definitions that reference vault. Naturally, I asked them to stop doing that...
If overload is the problem, I'd suggest that making the site *less* reliable might eventually fix the problem. In particular, dropping requests for repomd.xml would probably shed a lot of load while still giving human users access to package files.
On 2/28/22 23:46, Simon Matter wrote:
Yes, also mostly down for me. Some requests were answered but unable to really use the site.
Is it just overloaded? I've seen a few examples recently of people building CentOS 8 containers by building repo definitions that reference vault. Naturally, I asked them to stop doing that...
If overload is the problem, I'd suggest that making the site *less* reliable might eventually fix the problem. In particular, dropping requests for repomd.xml would probably shed a lot of load while still giving human users access to package files.
In my case I was just trying with firefox to get some files and browsing wasn't possible at all. Suddenly some pages were shown and then connection was stuck again. However, currently it works fine for me.
Simon
On 2022/03/01 10:35 a.m., Simon Matter wrote:
On 2/28/22 23:46, Simon Matter wrote:
Yes, also mostly down for me. Some requests were answered but unable to really use the site.
Is it just overloaded? I've seen a few examples recently of people building CentOS 8 containers by building repo definitions that reference vault. Naturally, I asked them to stop doing that...
If overload is the problem, I'd suggest that making the site *less* reliable might eventually fix the problem. In particular, dropping requests for repomd.xml would probably shed a lot of load while still giving human users access to package files.
In my case I was just trying with firefox to get some files and browsing wasn't possible at all. Suddenly some pages were shown and then connection was stuck again. However, currently it works fine for me.
I've been unable to access it at all for the past couple of days, either through a browser or yum.
Nels Lindquist ---- nlindq@maei.ca
On Tue, 1 Mar 2022 16:36:55 -0700 Nels Lindquist wrote:
I've been unable to access it at all for the past couple of days, either through a browser or yum.
https://downforeveryoneorjustme.com/vault.centos.org
On Tue, 1 Mar 2022 16:36:55 -0700 Nels Lindquist wrote:
I've been unable to access it at all for the past couple of days, either through a browser or yum.
Doesn't help here because downforeveryoneorjustme.com is not working currently:
Error 520 Ray ID: 6ae04324820783 • 2022-03-02 07:23:20 UTC Web server is returning an unknown error You Browser Working
Frankfurt Cloudflare Working
downforeveryoneorjustme.com Host Error
Nice new world, clouds everywhere, how can they fail :)
Simon
On 2/03/22 12:36 pm, Nels Lindquist wrote:
On 2022/03/01 10:35 a.m., Simon Matter wrote:
On 2/28/22 23:46, Simon Matter wrote:
Yes, also mostly down for me. Some requests were answered but unable to really use the site.
Is it just overloaded? I've seen a few examples recently of people building CentOS 8 containers by building repo definitions that reference vault. Naturally, I asked them to stop doing that...
If overload is the problem, I'd suggest that making the site *less* reliable might eventually fix the problem. In particular, dropping requests for repomd.xml would probably shed a lot of load while still giving human users access to package files.
In my case I was just trying with firefox to get some files and browsing wasn't possible at all. Suddenly some pages were shown and then connection was stuck again. However, currently it works fine for me.
I've been unable to access it at all for the past couple of days, either through a browser or yum.
There are working mirrors you can use:
https://mirror.rackspace.com/centos-vault/
Peter
On 2022/03/01 6:00 p.m., Peter wrote:
On 2/03/22 12:36 pm, Nels Lindquist wrote:
On 2022/03/01 10:35 a.m., Simon Matter wrote:
On 2/28/22 23:46, Simon Matter wrote:
Yes, also mostly down for me. Some requests were answered but unable to really use the site.
Is it just overloaded? I've seen a few examples recently of people building CentOS 8 containers by building repo definitions that reference vault. Naturally, I asked them to stop doing that...
If overload is the problem, I'd suggest that making the site *less* reliable might eventually fix the problem. In particular, dropping requests for repomd.xml would probably shed a lot of load while still giving human users access to package files.
In my case I was just trying with firefox to get some files and browsing wasn't possible at all. Suddenly some pages were shown and then connection was stuck again. However, currently it works fine for me.
I've been unable to access it at all for the past couple of days, either through a browser or yum.
There are working mirrors you can use:
Whatever the issue was, it appears to be resolved now. No issues with vault.
But thanks for that; I'll be sure to try the vault mirrors in future should this problem recur!
Nels Lindquist ---- nlindq@maei.ca
-
Christopher Wensink -
Frank Cox -
Gordon Messmer -
Nels Lindquist -
Peter -
Simon Matter