Closed Bug 920494 Opened 12 years ago Closed 12 years ago

mm-osx-107-3.qa.scl3.mozilla.com needs to be restarted

Categories

(Infrastructure & Operations :: DCOps, task)

Product:
Infrastructure & Operations
Component:
DCOps
Platform:
All
macOS
Type:
task
Priority:
Not set
Severity:
major

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: AndreeaMatei, Unassigned)

Details

After an unresponding Finder issue on our mm-osx-107-3.qa.scl3.mozilla.com machine, I have restarted it and since then I'm unable to connect to it. Might be that's still shutting down. I would appreciate if you could please check it and ensure it's back on. Thanks
This is critical. We need this machine back asap for our todays beta update testing.
Severity: normal → critical
Summary: OS X machine down after restart → mm-osx-107-3.qa.scl3.mozilla.com needs to be restarted
We'll have someone onsite within two hours. Andreea, Henrik: what are our options if this is a hardware problem, such as a failed drive? How long would it take to configure a replacement? (Reducing priority as IT uses this field to trigger pager alerts)
Severity: critical → major
Lets hope it's not a failing drive. It will take me a while to get all setup. But I might be able to do it and have it ready before update tests are getting started. CC'ing Anthony so that he is aware of the problem.
Arriving on site, the host is powered on and I'm able to ping & ssh to it. I did not reboot or made any changes. Please try again and let me know. ssh mm-osx-107-3.qa.scl3.mozilla.com The authenticity of host 'mm-osx-107-3.qa.scl3.mozilla.com (10.22.73.55)' can't be established. RSA key fingerprint is 8a:24:c9:48:43:42:ba:d8:90:c1:d0:94:68:d5:0c:e2. Are you sure you want to continue connecting (yes/no)? ping mm-osx-107-3.qa.scl3.mozilla.com PING mm-osx-107-3.qa.scl3.mozilla.com (10.22.73.55): 56 data bytes 64 bytes from 10.22.73.55: icmp_seq=0 ttl=60 time=7.753 ms 64 bytes from 10.22.73.55: icmp_seq=1 ttl=60 time=10.483 ms
So I did notice Finder was unresponsive as mentioned by Andreea. Rebooted the host; should be accessible.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
The box is still not behaving normally. Even after the reboot, screensharing was using around 100% cpu when I tried to login. A second try was successful but opening Safari no windows was visible. So I rebooted the box once more. Now it seems to work. I will keep an eye on the box for the next couple of days. Thanks Vinh for getting it rebooted. I should have checked myself via SSH first. I will remember that.
If issues persist, I will run a hardware diagnostic. Will take a few hours.
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.