Last modified: 2013-07-22 01:20:28 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 T53366, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 51366 - 504 timeout with Parsoid service
504 timeout with Parsoid service
Status: RESOLVED WORKSFORME
Product: Parsoid
Classification: Unclassified
General (Other open bugs)
unspecified
PC Linux
: Unprioritized normal
: ---
Assigned To: Gabriel Wicke
aklapper-moreinfo
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-15 14:42 UTC by brunsa2
Modified: 2013-07-22 01:20 UTC (History)
1 user (show)

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


Attachments

Description brunsa2 2013-07-15 14:42:01 UTC
I currently have VisualEditor running on an Ubuntu Server with Nginx, MediaWiki version 1.22alpha, Node.js 0.8.22. I get timeouts (504) when trying to use the VisualEditor (running Parsoid in debug often gives messages such as:

T:html: {"type":"TagTk","name":"body","attribs":[],"dataAttribs":{}} {
 "0": "WARNING: RETRY:",
 "1": {
   "code": "ETIMEDOUT"
 }
} Retrying Page Fetch request for null, 4 remaining {
 "0": "WARNING: RETRY:",
 "1": {
   "code": "ETIMEDOUT"
 }
}

Retrying Page Fetch request for null, 3 remaining ). I've tried with as many possible headers from a REST client and do not get any errors from Parsoid with that.
Comment 1 ssastry 2013-07-15 15:20:02 UTC
Please come on #mediawiki-parsoid IRC channel to debug these issues.  It appears that Parsoid might be having trouble connecting with your mediawiki instance.
Comment 2 Andre Klapper 2013-07-15 22:37:09 UTC
See http://www.mediawiki.org/wiki/MediaWiki_on_IRC for information on IRC.
Comment 3 brunsa2 2013-07-22 01:20:28 UTC
I've upgrades both VisualEditor and Parsoid, after converting wiki installation to  use SSL and then turning it off, Parsoid spontaneously started working.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links