Thanks, seems to be fixed now. I had a mini heart attack thinking that vault is gone for good ;) We don’t have a local mirror, probably we should start thinking about it, but its one of those things that if you keep putting off tend to resolve themselves.
> On 30. Jul 2024, at 15:35, Fabian Arrotin <arrfab@xxxxxxxxxx> wrote:
>
> On 30/07/2024 15:20, Aleksandar Ivanisevic wrote:
>> Hi,
>> currently im getting a 502 trying to get AppStream/repomd.xml, but some other files are fine, like repomd.asc, see below
>> is this an outage or it is gone forever?
>> ~$ curl 'https://vault.centos.org/centos/8-stream/AppStream/x86_64/os/repodata/repomd.xml'
>> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd";>
>> <HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
>> <TITLE>ERROR: The request could not be satisfied</TITLE>
>> </HEAD><BODY>
>> <H1>502 ERROR</H1>
>> <H2>The request could not be satisfied.</H2>
>> <HR noshade size="1px">
>> CloudFront wasn't able to connect to the origin.
>> We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
>> <BR clear="all">
>> If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.
>> <BR clear="all">
>> <HR noshade size="1px">
>> <PRE>
>> Generated by cloudfront (CloudFront)
>> Request ID: ZdkR1vn61GyMwUbRuoWv6MZULUJ2HyUNwwwsWi6xVY9v27hMZ8uZQA==
>> </PRE>
>> <ADDRESS>
>> </ADDRESS>
>> </B
>> ~$ curl 'https://vault.centos.org/centos/8-stream/AppStream/x86_64/os/repodata/repomd.xml'
>> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd";>
>> <HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
>> <TITLE>ERROR: The request could not be satisfied</TITLE>
>> </HEAD><BODY>
>> <H1>502 ERROR</H1>
>> <H2>The request could not be satisfied.</H2>
>> <HR noshade size="1px">
>> CloudFront wasn't able to connect to the origin.
>> We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
>> <BR clear="all">
>> If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.
>> <BR clear="all">
>> <HR noshade size="1px">
>> <PRE>
>> Generated by cloudfront (CloudFront)
>> Request ID: ZdkR1vn61GyMwUbRuoWv6MZULUJ2HyUNwwwsWi6xVY9v27hMZ8uZQA==
>> </PRE>
>> <ADDRESS>
>> </ADDRESS>
>> </BODY></HTML>~$ ~$ curl 'https://vault.centos.org/centos/8-stream/AppStream/x86_64/os/repodata/repomd.xml.asc'
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1
>> iQIcBAABCAAGBQJmXXXxAAoJEAW1VbOEg8ZdCTQP/RpadNlDi2Vk+AnKBz6pATni
>> YK6sCSxnSuWl/bIlMW6SnvKkrr98rMkHr6j6fH2YOGEenb8WPAUaa5+EPrqXAUBI
>> Wr6pirbEjmwqLr2BUh59otjWiNIxK4D02cqKnuGMBUh0N4ZhF6/Qsr3twlJSmDCl
>> WoRAB3ZTzavJmF3XGtUl8OuzyZDswZTUjP1ULGFMihBLWWPrLX2fSDvURle3Prcx
>> z+XbES18OuI2uhyTPqb+q1iIL3m9/JZFQceUNHDXXEu0PlLp+ROq4NTrsFxmmn+Z
>> +4y2ZJiRNIR3UlMDJhh6bRhSn7xOZr18yljwwkidtqrqxSJANLq0MGupiyT0gRAB
>> cmfSAjHd5yXODyiiCUGFZA0A4bGXp6tFyE1nLk5P6rehL8AQuPVKb1GKA6yP9StS
>> HTOeK/MSfyHrCvLXzCD7+9ryEdgpgQBCuJJGm46ppRPqkCvuTgmbQUd6zIK7PcaB
>> JR7qqPpG77K0k7Sp7p2+e5I/vBn0o5v3+LshLZq3otF1ueQM5zhR54xgs4gwUARG
>> gIE/cbO97yZzR97keGKGHMRCPNhMbwtTz0b+IeOsVEY5NEiwiFQCG/bvS6r6QnoA
>> JVOH8AfpDay/fRY6fLfaPatn6zE9vV+Mqel/BLl9Hdky53cMw2PjE+MtJHIZLjmT
>> 9JuOUkap7kzW8PXeeAa1
>> =6YJB
>> -----END PGP SIGNATURE-----
>
> There was a temporary issue reaching one of the origin nodes at the Cloudfront level, so some things were served from cache (edge nodes) while other couldn't be retrieved
> But afaics, it's all working now (tested from Europe)
>
> --
> Fabian Arrotin
> The CentOS Project | https://www.centos.org
> gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]
>
> _______________________________________________
> Discuss mailing list -- discuss@xxxxxxxxxxxxxxxx
> To unsubscribe send an email to discuss-leave@xxxxxxxxxxxxxxxx
_______________________________________________
Discuss mailing list -- discuss@xxxxxxxxxxxxxxxx
To unsubscribe send an email to discuss-leave@xxxxxxxxxxxxxxxx
