Closed Bug 932002 Opened 11 years ago Closed 11 years ago

mm-ci-master.qa.scl3.mozilla.com is not accessible

Categories

(Mozilla QA Graveyard :: Infrastructure, defect)

Product:
Mozilla QA Graveyard
Component:
Infrastructure
Type:
defect
Priority:
Not set
Severity:
blocker

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: u279076, Unassigned)

Details

I'm trying to load mm-ci-master.qa.scl3.mozilla.com:8080 to run some ondemand Mozmill tests for the Firefox 25 release and it's not loading. I've tried reconnecting to VPN serveral times and it's not working. I had Matt Wobensmith try as well and he was unable to connect. Stranglely though I am able to ping the server, ~59ms ping times with 0% packet loss.
It should be noted that this blocks releasing Firefox 25, 17.0.10esr, and 24.1.0esr.
Jenkins was using all the memory again and caused a 100% cpu load. Triggering a GC manually had no effect. Looking at iostats hasn't shown any anormal disk behavior. So I really would be interested to see which threads inside Java are consuming that amount of cpu load. But not sure how to further debug this. Dave, do you have any idea?

Jenkins master has been restarted now and should work as expected. All nodes are connected again.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
It could be worthwhile adding the Monitoring plugin [1] to Jenkins to see if that highlights anything.

[1] https://wiki.jenkins-ci.org/display/JENKINS/Monitoring
Dave, would you mind doing that? I would be happy to give a quick r+ on it so we can push to production soon.
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.