Last modified: 2013-03-05 17:39:29 UTC
Visit http://commons.wikimedia.org/w/index.php?title=File%3ABaltsende_en_parende_kraanvogels-Stichting_Natuurbeelden-170687.webm Scroll to the bottom to "Download derivative". Try downloading the Ogg version. Expected: Ogg file Actual: 404 Note: also reproduceable by going to any place the video is visible (like the commons homepage right now) and trying to select the ogg transcode, though the info isn't as obvious. Aaron tells me there's a change in the operations/puppet Gerrit repo that fixes this that needs ops review.
*** Bug 45292 has been marked as a duplicate of this bug. ***
Files are still lost but the error message changed from 404 error: File not found The URL you requested was not f... to 404 Not Found The resource could not be f... transcode-reset now seems to fix the broken transcodes but I am unable to reset all transcodes of all video files.
I'm getting 401's on the files at https://commons.wikimedia.org/wiki/Commons:GLAMToolset_project/Sprint_Demos . Is that the same problem?
part of deploying the latest version of TMH requires running maintenance/moveTranscoded.php in extensions/TimedMediaHandler to move all derivatives to there new location. this needs to be done to fix the 404s
This is pretty critical as broken derivatives == broken video playback in articles for affected files. Increasing priority. If the step in comment 4 is all that's required, looks like it may not require ops support.
Reedy is currently running the moveTranscoded.php script mentioned above which is fixing this issue. Most media files are already corrected. ETA of script completion is unknown at this time. Reedy: Let this bug know when that script is successfully completed. Thanks.
(In reply to comment #6) > > Reedy: Let this bug know when that script is successfully completed. Thanks. Should be done now. Any wikis still on 1.21wmf9 (any wikipedia minus enwiki) might need it running on them when they've been moved to 1.21wmf10 as the script isn't there in wmf9..
Great, I'll keep this open until all wikis get the breakage/fix.
As everything is on wmf10 now (and testwiki etc. already on wmf11), are there any wikis left or can this be closed?
(In reply to comment #9) > As everything is on wmf10 now (and testwiki etc. already on wmf11), are there > any wikis left or can this be closed? I think so, everything should be fixed; I re-ran the script when the rest of the wikis were moved to wmf10. Please feel free to reopen this bug if anyone finds problems with it
