Last modified: 2014-02-14 14:09:13 UTC
Original bug tilte: Server error on http://wikimania2014.wikimedia.org/wiki/Special:MyLanguage/Main_Page That page you are sent to by Google when searching for "wikimania 2014". The page reads as follows: Wikimedia Foundation Error Our servers are currently experiencing a technical problem. This is probably temporary and should be fixed soon. Please try again in a few minutes. If you report this error to the Wikimedia System Administrators, please include the details below. Request: GET http://wikimania2014.wikimedia.org/wiki/Special:MyLanguage/Main_Page, from 91.198.174.67 via amssq57 amssq57 ([91.198.174.67]:3128), Varnish XID 922288847 Forwarded for: 217.186.201.65, 91.198.174.67 Error: 503, Service Unavailable at Fri, 14 Feb 2014 08:46:27 GMT Note that https://wikimania2014.wikimedia.org/wiki/Special:MyLanguage/Main_Page works
http://en.wikipedia.org/wiki/Selberg_sieve succeeds for me from a host in the US (logged out) and fails from a host in Europe (both logged out and logged in) with the 503 error message. https://en.wikipedia.org/wiki/Selberg_sieve succeeds from a host in Europe, both logged out and logged in.
I can reproduce the problem on HTTP, but cannot reproduce on HTTPS (as in: the page works). Connecting from a host in Europe, through the same server (amssq57).
I can also reproduce the problem from Europe (also server amssq57). HTTP gets an error, HTTPS works. > Request: GET http://wikimania2014.wikimedia.org/wiki/Special:MyLanguage/Main_Page, from 91.198.174.68 via amssq57 amssq57 ([91.198.174.67]:3128), Varnish XID 928287430 > Forwarded for: ***.***.***.***, 91.198.174.68 > Error: 503, Service Unavailable at Fri, 14 Feb 2014 10:32:22 GMT
Although they failed for me (using European host) when the bug was filed, both of http://wikimania2014.wikimedia.org/wiki/Special:MyLanguage/Main_Page http://en.wikipedia.org/wiki/Selberg_sieve are now working again for me (using the same European host).
Mark restarted Varnish backend on amssq57, and things work again. Thanks, Mark!
*** Bug 61365 has been marked as a duplicate of this bug. ***
Thanks for handling this so quickly and keeping this ticket updated! (I had the same issue yesterday late night on fr.wp.)