Page MenuHomeMiraheze

Connection to restbase (and possibly parsoid) failing on services*
Closed, ResolvedPublic

Description

Restbase on s2:

connect to address 51.89.160.141 and port 7231: Connection refused

S1:

connect to address 51.89.160.132 and port 7231: Connection refused

@Doug also reported parsoid timeouts when using VE & Ext:DT

Event Timeline

RhinosF1 triaged this task as High priority.Fri, Nov 6, 18:01
RhinosF1 created this task.

Exact error given when using Extension:DiscussionTools is Error contacting the Parsoid/RESTBase server: (curl error: 28) Timeout was reached (link).

Possibly related to this error (see screenshot below) when previewing a page in VisualEditor.

In irc-relay, @Paladox also mentioned we don't use RESTbase with VisualEditor for privacy reasons, essentially, with private wikis, but I'm wondering if we could possibly explore a RESTbase-enabled VE for public wikis and the current configuration without RESTbase for private wikis?

Cheers,
Doug

Related error:

Error contacting the Parsoid/RESTBase server: (curl error: 28) Timeout was reached

just encountered again on community noticeboard on metawiki. Seems to be some sort of internal limit restricting Parsoid, perhaps?

Related error, which is persistent, on metawiki related to DiscussionTools:

Error contacting the Parsoid/RESTBase server: (curl error: 52) Server returned nothing (no headers, no data)

Cookies were last cleared in the past couple days, so there definitely seems to be some sort of connection timeout issue with Parsoid and its connection to the RESTbase server.

Error contacting the Parsoid/RESTBase server: (curl error: 52) Server returned nothing (no headers, no data)
I have been getting this error on both metawiki and snapwikiwiki trying to use DiscussionTools' Reply feature.

If your using a chrome based browser you need to delete your cookies.

Paladox claimed this task.

Forgot to close this as resolved, but in any case the error show in the task description is not related to the above.

@Paladox I would like to procedurally reopen this task, and we can possibly mark it as stalled, if that's desired, as clearing one's entire cookies every 24 to 72 hours doesn't seem like a viable long term solution. Plus, we still have the recurring connection refused and connection timed out errors, which didn't occur with the previous VisualEditor-related issue to SameSite. As I think @Void mentioned elsewhere, likely in a Discord channel, I do suspect this is like due to one or two possible issues:

  1. Issue with the way our wiki farm manages the setting of cookies; and/or,
  2. Some sort of internal timeout limit with the Parsoid or RESTbase server.

Trusting we can either reopen or stall, rather than resolve, this unresolved task.

Thanks.

This task was about icinga reporting a specific issue with restbase.

The constant issues in VE etc with parsoid should be a seperate task.