[go: up one dir, main page]

Page MenuHomePhabricator

Specific user subpage on dewiki shows a PHP fatal error timeout
Closed, ResolvedPublic

Description

The site at https://de.wikipedia.org/wiki/Benutzer:Holger1959/HE-1 times out with the message:

PHP fatal error:
entire web request took longer than 60 seconds and timed out

If the site is loading please purge the cache (For @ToBeFree it worked until he purged): https://de.wikipedia.org/wiki/Benutzer:Holger1959/HE-1?action=purge

ToBeFree and me make the size of the data responsible for the error.

A possible solution as workarround is to clear the page by a system administrator.

Please call me the tag which sould be added next time if a technical problem appears.

Event Timeline

Aklapper renamed this task from PHP timeout on dewiki (just one Subpage) to Specific user subpage on dewiki shows a PHP fatal error timeout.Oct 1 2018, 3:15 PM

I believe that this page is placing an undue burden on the servers, violating the TOS. A friendly but effective solution would be a system administrator asking the user to fix this problem by contacting them via talk page or e-mail.

How can the user solve that if he cannot reach the page?

For the records, https://de.wikipedia.org/wiki/Benutzer:Holger1959/HE-1?action=raw allows seeing the full page content as a plain text file.

Oh nice a new command :) yeah it's a large page, I got 1.655 MBytes

The page history shows that the page is being bot-generated; the best solution here would probably just be to have the bot author rewrite the bot to split the page into more moderately-sized subpages.

Oh, interesting, this is @Magnus' bot? Ping :)

I can further limit the item number the bot accepts (though I have other people asking me to _increase_ it...).

Other possible solutions:

  • Change the query sparql=SELECT ?item WHERE { ?item wdt:P131 wd:Q1199 } to include LIMIT 1000 or the like
  • Change MediaWiki to not accept texts it can't display...

It just loaded for me without failing due to taking too long - including after a purge. The size when this was filed (1,655,523 bytes) vs now (1,157,263 bytes) may explain it. Is there anything else to be done here?

Pppery subscribed.

It just loaded for me without failing due to taking too long - including after a purge. The size when this was filed (1,655,523 bytes) vs now (1,157,263 bytes) may explain it. Is there anything else to be done here?

No response after 3 years, closing.