Last modified: 2014-07-24 21:00:40 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 T70405, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 68405 - 503s from Parsoid on test2wiki
503s from Parsoid on test2wiki
Status: RESOLVED FIXED
Product: Parsoid
Classification: Unclassified
General (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: Parsoid Team
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-07-22 21:50 UTC by Chris McMahon
Modified: 2014-07-24 21:00 UTC (History)
4 users (show)

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


Attachments
503 error from Parsoid on test2 (193.05 KB, image/png)
2014-07-22 21:50 UTC, Chris McMahon
Details

Description Chris McMahon 2014-07-22 21:50:57 UTC
Created attachment 16004 [details]
503 error from Parsoid on test2

Seen on test2wiki several times 22 July, see screen shot.
Comment 1 ssastry 2014-07-22 22:00:08 UTC
I pull production logs onto bast1001 and looked for anything odd, but couldn't find anything for the page in the screenshot.

ssastry@bast1001:~/logs$ grep test2wiki * | grep 0.229
wtp1015:[info][test2wiki/0.229214833204894_Moved] starting parsing
wtp1015:[warning][test2wiki/0.229214833204894_Moved?oldid=66911] Cache MISS: http://10.2.2.29/test2wiki/0.229214833204894_Moved?oldid=66910
wtp1015:[info][test2wiki/0.229214833204894_Moved?oldid=66911] completed parsing in 227 ms

Requires more investigation.
Comment 2 ssastry 2014-07-22 22:01:12 UTC
Load graphs also look normal here: https://ganglia.wikimedia.org/latest/?r=hour&cs=&ce=&m=cpu_report&s=by+name&c=Parsoid+eqiad&h=&host_regex=&max_graphs=0&tab=m&vn=&sh=1&z=small&hc=4 (the network traffic spike is me pulling the production logs).
Comment 3 Chris McMahon 2014-07-22 22:02:36 UTC
I have definitely seen Parsoid 503 several times today on test2wiki.
Comment 4 ssastry 2014-07-22 22:03:54 UTC
I believe you. I should have clarified that I am just recording information here as I look around.
Comment 5 ssastry 2014-07-22 22:19:55 UTC
I also verified that all parsoid nodes have the same version of the code (just to rule out the possibility of a bad deploy) by running "dsh -g parsoid -M curl http://127.0.0.1:8000/_version" on tin.
Comment 6 ssastry 2014-07-23 17:15:35 UTC
From #mediawiki-pdfhack @ 12:07 CST 
"<mwalker> cscott, morning; I have three patches for you :) also -- I've been getting a lot of 503s from parsoid lately"

We are now wondering if this could be from varnish that is sitting in front of the parsoid cluster.
Comment 7 Matt Walker 2014-07-23 18:01:48 UTC
I just dumped a couple of 503 responses; they look like this:

{
  "code": 503,
  "headers": {
    "server": "Varnish",
    "content-type": "text/html; charset=utf-8",
    "retry-after": "5",
    "content-length": "419",
    "accept-ranges": "bytes",
    "date": "Wed, 23 Jul 2014 18:00:14 GMT",
    "x-varnish": "1859100242",
    "age": "0",
    "via": "1.1 varnish",
    "connection": "close",
    "x-cache": "cp1045 frontend miss (0)"
  },
  "body": "\n<?xml version=\"1.0\" encoding=\"utf-8\"?>\n<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0 Strict//EN\"\n \"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd\">\n<html>\n  <head>\n    <title>503 Service Unavailable</title>\n  </head>\n  <body>\n    <h1>Error 503 Service Unavailable</h1>\n    <p>Service Unavailable</p>\n    <h3>Guru Meditation:</h3>\n    <p>XID: 1859100242</p>\n    <hr>\n    <p>Varnish cache server</p>\n  </body>\n</html>\n"
}
Comment 8 Gerrit Notification Bot 2014-07-24 01:26:49 UTC
Change 148924 had a related patch set uploaded by GWicke:
Bump Parsoid backend connection limit

https://gerrit.wikimedia.org/r/148924
Comment 9 Gerrit Notification Bot 2014-07-24 19:44:19 UTC
Change 148924 merged by Cmjohnson:
Bump Parsoid backend connection limit

https://gerrit.wikimedia.org/r/148924

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


Navigation
Links