Page MenuHomePhabricator

parsoidserver-http-bad-status
Closed, DeclinedPublic

Description

http://en.m.wikipedia.beta.wmflabs.org/w/api.php?format=json&action=visualeditor&paction=parse&page=Selenium_Edit_Test

Any idea why this request ends up with the response:
{"servedby":"deployment-apache32","error":{"code":"parsoidserver-http-bad-status","info":"404"}}

It prevents VisualEditor from loading on mobile...


Version: unspecified
Severity: normal

Details

Reference
bz60755

Event Timeline

bzimport raised the priority of this task from to Needs Triage.Nov 22 2014, 3:05 AM
bzimport added a project: Parsoid-Web-API.
bzimport set Reference to bz60755.

The problem is not limited to the mobile version, it also happens on the Web using both Firefox and Chrome, both Monobook and Vector.
Example response: (on it.wiki user sandbox, but it also applies to en.wiki NS:0)

{"servedby":"mw1121","error":{"code":"parsoidserver-http-timed-out","info":"http://10.2.2.29/itwiki/Utente%3ABaruneju%2Fsandbox2?oldid=63854985"}}

This page loads for me: http://parsoid-lb.eqiad.wikimedia.org/itwiki/Utente%3ABaruneju%2Fsandbox2?oldid=63854985

Sometimes issues in the MW API are misreported as 404s on our end, so maybe this was a transient API failure. The misleading error reporting is tracked in bug 58390.

The API issues were probably the internal LVS failure today, caused by a networking configuration error. See Mark's mail titled "Outage report: LVS outage February 3, 2013" on the ops list.

I'm closing this bug as worksforme, as the underlying API outage has since been fixed. Bug 58390 tracks the error code issue.