VisualEditor doesn't work on the beta-cluster
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	Amire80
	May 18 2015, 7:34 AM

Description

When trying to write and save something in VisualEditor in the beta cluster, I repeatedly get a "parsoidserver-http: HTTP 0" error and the page is not saved.

Related Objects
Search...

Status	Assigned	Task
Resolved	• mobrovac	T99496 VisualEditor doesn't work on the beta-cluster
Resolved	• mobrovac	T99505 Parsoid not binding to any port in Beta Cluster
Resolved	Andrew	T99521 No DNS entry for deployment-logstash1.eqiad.wmflabs ?

Event Timeline

Amire80 created this task.May 18 2015, 7:34 AM

Amire80 raised the priority of this task from to Needs Triage.

Amire80 updated the task description. (Show Details)

Amire80 added projects: Continuous-Integration-Infrastructure, VisualEditor, Parsoid.

Amire80 subscribed.

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptMay 18 2015, 7:34 AM

This is caused by a problem in the VE <-> RESTBase communication. There seem to be two problems:

VE in Beta is trying to use the /api/rest_v1/ route to access RB, but gets a 404 (e.g. http://en.wikipedia.beta.wmflabs.org/api/rest_v1/page/html/0.2891918462743097/59262)
RESTBase keeps failing on deployment-restbase01 in deployment-prep

I'm currently investigating the latter. The former will probably need some path adjustments in mw-config.

• mobrovac claimed this task.May 18 2015, 8:27 AM

• mobrovac triaged this task as Unbreak Now! priority.

• mobrovac edited projects, added Beta-Cluster-Infrastructure, RESTBase; removed Parsoid, Continuous-Integration-Infrastructure.

• mobrovac set Security to None.

• mobrovac added a subtask: T99505: Parsoid not binding to any port in Beta Cluster.May 18 2015, 9:14 AM

In T99496#1292834, @mobrovac wrote:

This is caused by a problem in the VE <-> RESTBase communication. There seem to be two problems:

VE in Beta is trying to use the /api/rest_v1/ route to access RB, but gets a 404 (e.g. http://en.wikipedia.beta.wmflabs.org/api/rest_v1/page/html/0.2891918462743097/59262)

Actually the route works just fine. The 404 originates from Varnish which gets an ECONNREFUSED from RESTBase after it fails.