504 Gateway Time-out nginx

Jump to navigation Jump to search

Please summarize the below thread in the editing box. You may use any wikitext in your summary. When you finish, click "Publish changes".

You do not have permission to edit this page, for the following reason:

The action you have requested is limited to users in the group: Users.


You can view and copy the source of this page.

Return to Summary:Support/504 Gateway Time-out nginx.

I got a "series of 504 Gateway Time-out"s during the recent minutes.

Purodha Blissenbach (talk)11:32, 17 May 2015

Server was overloaded at 13.38 CEST and got better by 13.41. I suggest to avoid doing expensive things like opening many tabs or using Special:SearchTranslations intensively. Can you defer your mass-reporting till after the translation rally?

Nemo (talk)11:52, 17 May 2015

I got two more such series, one is just over. Looks like Weekend-translation-rally-time :-)

Purodha Blissenbach (talk)16:23, 17 May 2015

I got the same error a few times.

 
 

I've closed this issue. The time-outs are related to a lack of server resources, mainly because ElastisSearch is enormously CPU hungry. We are in the process of requesting more computing resources from our hosting sponsor netcup.de. If we get the requested resources, we can upgrade our current installation to be much quicker...

Siebrand11:58, 25 May 2015