Last modified: 2013-10-11 20:06:47 UTC
Currently I am getting "504 Gateway Time-out / nginx/1.1.19" when editing pages with a lot of transclusions, like https://commons.wikimedia.org/wiki/User:Raymond/People (see URL for the latest diff). Page was saved succesfully. I know that I am near one of the parser limits: NewPP limit report Preprocessor visited node count: 219143/1000000 Preprocessor generated node count: 86968/1500000 Post‐expand include size: 1902661/2048000 bytes Template argument size: 846363/2048000 bytes Highest expansion depth: 34/40 Expensive parser function count: 0/500 Saved in parser cache with key commonswiki:pcache:idhash:6276849-0!*!0!dmy!*!de!5!* and timestamp 20130618070841 In the past when I exceed "Post‐expand include size" at least I got no 504 but transclusion fails only.
This issue was reported quite often during the last month: Sep 9 on de.wikipedia [1] Sep 24-26 on en.wikipedia (various reports) [2] Oct 8 on de.wikipedia [3] At least the two examples from de.wikipedia use many transclusions, but they all worked in the past, so this might be related to bug 54876, where the long logs worked in the past, too, and only recently started to throw this "504 Gateway Time-out by nginx" error. [1] https://de.wikipedia.org/wiki/Wikipedia:Fragen_zur_Wikipedia/Archiv/2013/Woche_37#504_Gateway_Time-out_beim_Speichern [2] https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29/Archive_117#Is_preview_slower_than_usual.3F [3] https://de.wikipedia.org/wiki/Wikipedia:Fragen_zur_Wikipedia#Liste_der_Gro.C3.9F-_und_Mittelst.C3.A4dte_in_Deutschland
Got this error on nl-wiki on https://nl.wikipedia.org/w/index.php?title=Lijst_van_rijksmonumenten_in_Den_Haag (never got it before on similar and larger monuments lists). On both the Den Haag list and the Middelburg list (second largest) I also got "Our servers are currently experiencing a technical problem. This is probably temporary and should be fixed soon. Please try again in a few minutes." In all occasions the edits were saved (after a long loading time). Recent changes to the template were reverted by me, but still the same problems occured (so rereverted them again).
Shouldn't this be a higher priority? It seems to me pretty ofsetting for (new) users when they get an error in an occasion where seemingly nothing is wrong.
