Closed Bug 1161908 Opened 9 years ago Closed 9 years ago

No connection to mm-osx-107-1.qa.scl3.mozilla.com

Categories

(Infrastructure & Operations :: DCOps, task)

Product:
Infrastructure & Operations
Component:
DCOps
Type:
task
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: whimboo, Unassigned)

Details

(Whiteboard: [qa-automation-blocked]) 

About 7h ago the machine went down and didn't come back. I cannot login via SSH nor ping it.

$ ping 10.22.73.53
PING 10.22.73.53 (10.22.73.53) 56(84) bytes of data.
^C
--- 10.22.73.53 ping statistics ---
15 packets transmitted, 0 received, 100% packet loss, time 14111ms

Can someone please restart the machine? We need it for Mozmill tests. Thanks.
wrong hostname? looks 10.22.73.53 is up now as well.

vans-MacBook-Pro:~ vle$ fping 10.22.73.53
10.22.73.53 is alive
vans-MacBook-Pro:~ vle$ host 10.22.73.53
53.73.22.10.in-addr.arpa domain name pointer mm-osx-107-1.qa.scl3.mozilla.com.


The authenticity of host 'mm-osx-107-2.qa.scl3.mozilla.com (10.22.73.54)' can't be established.
RSA key fingerprint is 6f:38:17:d4:92:f5:90:0d:db:38:34:3e:f6:0b:fe:8c.
Are you sure you want to continue connecting (yes/no)? no
Host key verification failed.
vans-MacBook-Pro:~ vle$ fping !$
fping mm-osx-107-2.qa.scl3.mozilla.com
mm-osx-107-2.qa.scl3.mozilla.com is alive
vans-MacBook-Pro:~ vle$ ssh !$
ssh mm-osx-107-2.qa.scl3.mozilla.com
The authenticity of host 'mm-osx-107-2.qa.scl3.mozilla.com (10.22.73.54)' can't be established.
RSA key fingerprint is 6f:38:17:d4:92:f5:90:0d:db:38:34:3e:f6:0b:fe:8c.
Are you sure you want to continue connecting (yes/no)?
Status: NEW → RESOLVED
colo-trip: --- → scl3
Closed: 9 years ago
Resolution: --- → FIXED
Sorry, the IP was correct but not the machine name. So have you done anything to the mm-osx-107-1 box? I see that it came back about 3h ago. I would be interested what the problem was, or what you did.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Summary: No connection to mm-osx-107-2.qa.scl3.mozilla.com → No connection to mm-osx-107-1.qa.scl3.mozilla.com
the connection on the mini was loose so i replaced the cable. i think as these chassis houses 4 minis per 1u, the heat might have may caused the plastic in the clip to expand, making it partially slip out of the ethernet port as this is the same rack slot we were troubleshooting the bad mini a few months ago.
Status: REOPENED → RESOLVED
Closed: 9 years ago → 9 years ago
Resolution: --- → FIXED
That would explain why it auto-connected. Thanks Van for the detailed description. All fine then.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.