Steps to replicate the issue (include links if applicable):
What happens?:
If you report this error to the Wikimedia System Administrators, please include the details below. Request from (European IP redacted) via deployment-cache-upload08.deployment-prep.eqiad1.wikimedia.cloud, ATS/9.1.4 Error: 500, Cannot find server. at 2024-03-10 17:24:36 GMT
What should have happened instead?:
Bert
I'm afraid SREs cannot help here- while it is ATS returning the error to the end user, it is not the source, it is upload.wikimedia.beta.wmflabs.org what is timing out (Failed to connect to upload.wikimedia.beta.wmflabs.org port 443: Connection timed out) , which means it is a beta issue, that we don't own. I couldn't find any team responsible for it at: https://www.mediawiki.org/wiki/Developers/Maintainers#Services_and_administration so returning it to the original tagging.
So nobody is responsible for this.
People are still uploading files to betacommons, but I can't check them for copyvios -or worse-. And if you break thumbnails or anything file-related? Nobody will know until it hits production.
Only way to view anything is to delete it and use Special:Undelete to view it!
See T215217: deployment-prep (beta cluster): Code stewardship request and its subtasks for the general problem.
;-(
https://commons.wikimedia.beta.wmflabs.org/w/thumb.php?f=Example.jpg&w=220 doesn't work either, but returns instantly instead of taking ~45s:
Request from (European IP redacted) via deployment-cache-text08 deployment-cache-text08, Varnish XID 396622189 Upstream caches: deployment-cache-text08 int Error: 500, Internal Server Error at Thu, 28 Mar 2024 16:59:52 GMT
Compare to https://upload.wikimedia.beta.wmflabs.org/wikipedia/commons/a/a9/Example.jpg:
Request from (European IP redacted) via deployment-cache-upload08.deployment-prep.eqiad1.wikimedia.cloud, ATS/9.1.4 Error: 500, Cannot find server. at 2024-03-28 17:03:14 GMT
This may be related to T360595 I know the caching hosts use varnishkafka and if kafka does not have a valid ssl cert then...maybe that's a problem here.