BzAPI cannot connect to bugzilla.mozilla.org

RESOLVED FIXED

Status

mozilla.org Graveyard
Server Operations
--
blocker
RESOLVED FIXED
7 years ago
3 years ago

People

(Reporter: Away for a while, Assigned: justdave)

Tracking

Details

(URL)

(Reporter)

Description

7 years ago
This is what I'm getting.

--- 
error: 1
http_code: 500
message: "HTTP Error: 500 Can't connect to bugzilla.mozilla.org:443 (SSL connect attempt failed with unknown errorerror:00000000:lib(0):func(0):reason(0))"
(Reporter)

Comment 1

7 years ago
I also got this error when filing this very bug, even though the bug had been entered to the db:

Service Unavailable

The service is temporarily unavailable. Please try again later.

Updated

7 years ago
Assignee: server-ops → justdave
This was deliberately blocked because someone was hitting it too hard and buried Bugzilla.  As I have no way to block people hitting BzAPI (we don't maintain it), all I could do to keep Bugzilla itself up and running was block the whole thing.
Servers have all recovered now, I've re-enabled this, and watching it still.

Comment 4

7 years ago
https://api-dev.bugzilla.mozilla.org/latest/count?product=Bugzilla&priority=P1&severity=blocker gives me 

--- 
error: 1
http_code: 500
message: "HTTP Error: 500 Internal Server Error"

and the json outputs return 

HTTP/1.1 400 Bad Request
(Reporter)

Comment 5

7 years ago
This is happening again.  A lot of services depend on BzAPI now.  Is there anything which can be done here?
Ehsan: a timed-out addition of a custom field to Bugzilla caused Bugzilla's reporting function (which BzAPI uses) to break. This is not a BzAPI problem. And it's being tracked in bug 611356. :-)

Gerv
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Since bug 611356 got fixed, I believe this is, now, too.
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.