[go: up one dir, main page]

Page MenuHomePhabricator

Persistent 404 errors for some Commons files, fixable by overwriting
Closed, ResolvedPublicBUG REPORT

Description

Steps to replicate the issue (include links if applicable):

What happens?:

An error page: "File not found: /v1/AUTH_mw/wikipedia-commons-local-public.80/8/80/Ford_at_Little_Stretton_-_geograph.org.uk_-_4597830.jpg"

What should have happened instead?:

My browser should have displayed a picture like that at https://www.geograph.org.uk/photo/4597895

Other information (browser name/version, screenshots, etc.):

The problem affects thumbnails as well as the original version of the file. I found the problem using Firefox 102.9.0esr. I was able to reproduce it on Toolforge using Wget:

bjh21@tools-sgebastion-10:~$ wget https://upload.wikimedia.org/wikipedia/commons/8/80/Ford_at_Little_Stretton_-_geograph.org.uk_-_4597830.jpg
--2023-04-09 11:19:26--  https://upload.wikimedia.org/wikipedia/commons/8/80/Ford_at_Little_Stretton_-_geograph.org.uk_-_4597830.jpg
Resolving upload.wikimedia.org (upload.wikimedia.org)... 208.80.154.240, 2620:0:861:ed1a::2:b
Connecting to upload.wikimedia.org (upload.wikimedia.org)|208.80.154.240|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2023-04-09 11:19:27 ERROR 404: Not Found.

I've noticed this problem affecting several files uploaded by GeographBot:

For the last of those, I was able to work around the problem by overwriting the file with a different one. When I did that, the original version appeared properly in the file history, and when I reverted to that version it became available under the original URL. This suggests that the files do exist, and it might be possible to make the visible without leaving permanent ugliness in their file histories.

It's possible that this problem also affects files from other sources: I haven't made any attempt at looking for them.

I think this is a different problem from T331820 because it affects original images and not just thumbnails.

Related Objects

Event Timeline

It looks like all of these files are now working properly, so at least this instance of the problem is resolved.

There's a weekly job that runs on Monday mornings that attempts to pick up any objects (originals only) that got written to the primary DC but not the secondary, so it's certainly possible that's what fixed these given when you reported it.

Resolving per last two comments