Getting Service Unavailable during test runs doing searches

VERIFIED FIXED

Status

mozilla.org Graveyard
Server Operations
--
major
VERIFIED FIXED
7 years ago
3 years ago

People

(Reporter: automatedtester, Assigned: cshields)

Tracking

Details

(Whiteboard: [fromAutomation], URL)

(Reporter)

Description

7 years ago
While doing an empty search(litmus 13847) and a unicode search(litmus 13697) we are getting service unavailable.

Our automated tests took screenshots of the failures

http://qa-selenium.mv.mozilla.com:8080/job/input%20stage/349/artifact/input.stage.mozilla.com_1298477413.png 

http://qa-selenium.mv.mozilla.com:8080/job/input%20stage/349/artifact/input.stage.mozilla.com_1298477448.png
(Reporter)

Updated

7 years ago
Flags: in-testsuite+
Target Milestone: --- → 3.3
Whiteboard: [fromAutomation]
CCing cshields: QA seems to be getting this kind of error relatively frequently lately. As you can see from the styling of the error message, this is not an error directly in the app, but thrown by Zeus. Any idea when Zeus would bring up this kind of page, and what could cause this in our case?

Do you guys have any graphs on the load of the staging boxes? Perhaps something's going on on one of the affected servers that takes it down for a limited amount of time. This particular build was kicked off at 8am[1], so perhaps some cron job ran.

[1] http://qa-selenium.mv.mozilla.com:8080/job/input%20stage/349/
Punting this to 3.4 for now. It's not an error in the app so shouldn't delay this milestone.
Target Milestone: 3.3 → 3.4
(Reporter)

Comment 3

7 years ago
http://qa-selenium.mv.mozilla.com:8080/job/input%20stage/396/ 7 tests failing because of this...

Updated

7 years ago
Assignee: nobody → fwenzel
OS: Mac OS X → All
Hardware: x86 → All
+1 Our automated tests are failing 3 out of 4 runs due to this.
Assignee: fwenzel → nobody

Updated

7 years ago
Assignee: nobody → server-ops
Component: Input → Server Operations
Flags: in-testsuite+
Product: Webtools → mozilla.org
QA Contact: input → mrz
Target Milestone: 3.4 → ---
Version: Trunk → other

Updated

7 years ago
Severity: normal → major

Updated

7 years ago
Assignee: server-ops → cshields
(Reporter)

Comment 6

7 years ago
We are hoping to have a Test Day against this staging server on Tuesday and would be great if we can try stabilize this before hand
(Assignee)

Comment 7

7 years ago
Is this related to 644302??
(Reporter)

Comment 8

7 years ago
Think they might be related
(In reply to comment #7)
> Is this related to 644302??

I am working on making some SQL for IT to run that'd reduce the weight of this query, in both prod and stage.
See Also: → bug 644302
(Assignee)

Comment 10

7 years ago
marking this dependent upon 644302, which is pending verification
Depends on: 644302
(Assignee)

Comment 11

7 years ago
So is this fixed now?
(Reporter)

Comment 12

7 years ago
We have had over 12 builds on our CI that havent encountered this problem.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Marking as verified FIXED based on comment 12, and http://qa-selenium.mv.mozilla.com:8080/job/input%20stage/buildTimeTrend
Status: RESOLVED → VERIFIED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.