Page MenuHomePhabricator

(HTTP) 504 Gateway Timeout error when trying to save
Closed, DuplicatePublic

Description

This task is about restoring the ability to save an edit on this Office wiki page: https://office.wikimedia.org/wiki/Community_Relations_Specialists/Audiences/Meetings_with_Product

I suspect this has something to do with the size of the page; I have NOT had issues trying to save to other pages. See diff: https://w.wiki/ZE2.

Behavior

  1. Visit: This task is about restoring the ability to save an edit on this Office wiki page: https://office.wikimedia.org/wiki/Community_Relations_Specialists/Audiences/Meetings_with_Product
  2. Edit the page in some way using the visual or wikitext editor

Actual

  1. ❗️Notice an error is presented that reads: Something went wrong / Error contacting the Parsoid/RESTBase server (HTTP 504)

Expected

  1. ✅Notice the edit you made in "Step 2" is successfully published to the page

Environment

  • Browser: Chrome 84.0.4147.89
  • OS: macOS 10.15.4

Event Timeline

ssastry triaged this task as Medium priority.Aug 10 2020, 6:09 PM
ssastry moved this task from Needs Triage to Bugs & Crashers on the Parsoid board.

On some VE edits, when I click 'Review Changes' or switch to 'Source Editing', the request goes through just fine. But, on some requests, I get the error / page hangs.

Unfortunately, I couldn't find any Parsoid-PHP log entries for officewiki. But, when I expanded my search to all logstash events, I found https://logstash.wikimedia.org/goto/bedbf8dd6b360e16945d63c0a9df13f7

So, a number of ApiParsoidTrait::transformHTML: Received funny ETag from client: {etag} and ApiParsoidTrait::requestRestbase: Received HTTP {code} from RESTBase which are the http 504s. All errors are for transform/html/to/wikitext/Community_Relations_Specialists%2FAudiences%2FMeetings_with_Product/$OLDID.

Do @Pchelolo or @matmarex know what these are about?

There are a couple of hits on 2020-08-10. Looks like the etag is the empty string (or null or undefined, I don't know exactly how those are being stringified).

EDIT: indeed, I suspect 'null' is indistinguishable from the empty string here.

This was probably the same problem as T244609 (because the page causing issues here is huge like in that task, and it's the same error message).