Last modified: 2014-02-06 01:51:27 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T62755, the corresponding Phabricator task for complete and up-to-date bug report information.

Bug 60755 - parsoidserver-http-bad-status


Summary:	parsoidserver-http-bad-status

Status:	RESOLVED WORKSFORME

Product:	Parsoid
Classification:	Unclassified
Component:	Web API (Other open bugs)
Version:	unspecified
Hardware:	All All

Importance:	Unprioritized normal
Target Milestone:	---
Assigned To:	Gabriel Wicke

URL:
Whiteboard:
Keywords:

Depends on:	58390
Blocks:
	Show dependency tree / graph

Reported:	2014-02-03 06:15 UTC by Jon
Modified:	2014-02-06 01:51 UTC (History)
CC List:	5 users (show)

See Also:
Web browser:	---
Mobile Platform:	---
Assignee Huggle Beta Tester:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Jon 2014-02-03 06:15:57 UTC

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...

Comment 1 Giuseppe 2014-02-03 11:41:48 UTC

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"}}

Comment 2 Gabriel Wicke 2014-02-03 19:30:28 UTC

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.

Comment 3 Gabriel Wicke 2014-02-03 21:45:20 UTC

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.

Comment 4 Gabriel Wicke 2014-02-06 01:51:27 UTC

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

Wikimedia Bugzilla is closed!

Search

Personal tools

Navigation

Links