Last modified: 2014-11-05 00:40:21 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 T74982, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 72982 - API error: unable to connect to redis
API error: unable to connect to redis
Status: NEW
Product: Wikimedia Labs
Classification: Unclassified
deployment-prep (beta) (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2014-11-04 21:29 UTC by Chris McMahon
Modified: 2014-11-05 00:40 UTC (History)
8 users (show)

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

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

Description Chris McMahon 2014-11-04 21:29:33 UTC 
Browser tests on beta labs have been getting a fair number of these in recent times: 

Exception Caught: Unable to connect to redis server. (internal_api_error_JobQueueConnectionError) (MediawikiApi::ApiError)

Often in conjunction with other API errors "Our servers are currently experiencing a technical problem. This is probably temporary and should be fixed soon." reporting a 503
Comment 1 Greg Grossmeier 2014-11-04 22:50:50 UTC 
Chris: can you see if this is related (or not) to runs of scap on Beta Cluster a la bug 72366? 503s are now suspicious to me :)
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links