Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

media.ccc.de in confused state about some 38C3 uploads #771

Closed
HW42 opened this issue Jan 2, 2025 · 1 comment
Closed

media.ccc.de in confused state about some 38C3 uploads #771

HW42 opened this issue Jan 2, 2025 · 1 comment
Assignees
Labels

Comments

@HW42
Copy link

HW42 commented Jan 2, 2025

The mirror management seems to be in a confused state about some of the recent 38C3 uploads.

I have seen this with different files, arbitrary example:

https://media.ccc.de/v/38c3-security-nightmares under Downloads links to https://cdn.media.ccc.de/congress/2024/webm-sd/38c3-533-deu-eng-Security_Nightmares_webm-sd.webm

When trying to download I get redirects (from multiple tries):

https://silo.ffmuc.net/38c3/congress/2024/webm-sd/38c3-533-deu-eng-Security_Nightmares_webm-sd.webm
https://media.nurluefter.de/congress/2024/webm-sd/38c3-533-deu-eng-Security_Nightmares_webm-sd.webm
https://ftp.halifax.rwth-aachen.de/ccc/congress/2024/webm-sd/38c3-533-deu-eng-Security_Nightmares_webm-sd.webm

Only the last mirror actually has the file. Others deliver an 404 error.

If I look at the directory listing at https://cdn.media.ccc.de/congress/2024/webm-sd/, I see:

38c3-533-deu-eng-Security_Nightmares_webm-sd.webm  02-Jan-2025 00:20           216476191

But when looking at the https://cdn.media.ccc.de/congress/2024/webm-sd/38c3-533-deu-eng-Security_Nightmares_webm-sd.webm?mirrorlist it says:

The file /congress/2024/webm-sd/38c3-533-deu-eng-Security_Nightmares_webm-sd.webm has a size of 0.0 bytes (0 bytes) and was last modified on Mon, 01 Jan 0001 00:00:00 UTC.

So clearly something is in a somewhat confused or half-uploaded state.

Might be the same as reported in #754, but since that one has been closed by the reported, and it's not obvious if it's the same or a different error, I'm opening a new issue.

PS: The above is what I observed within the last 30 min or so (as of 2025-01-03 00:20 +01:00).

@lukas2511
Copy link
Member

This was a temporary issue while our cdn was effectively down and some emergency fallback redirects™ were in place.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants