Status

mozilla.org Graveyard
Server Operations
--
major
RESOLVED FIXED
4 years ago
3 years ago

People

(Reporter: ewong, Assigned: gcox)

Tracking

Details

(Reporter)

Description

4 years ago
Cannot seem to ssh into it:

[ewong@jump1.community.scl3 ~]$ ssh -l seabld sea-master1
ssh: connect to host sea-master1 port 22: No route to host

Nor ping it:

[ewong@jump1.community.scl3 ~]$ ping sea-master1
PING sea-master1.community.scl3.mozilla.com (63.245.223.11) 56(84) bytes of data
.
From jump1.community.scl3.mozilla.com (63.245.223.8) icmp_seq=2 Destination Host Unreachable
From jump1.community.scl3.mozilla.com (63.245.223.8) icmp_seq=3 Destination Host Unreachable
From jump1.community.scl3.mozilla.com (63.245.223.8) icmp_seq=4 Destination Host Unreachable
(Reporter)

Comment 1

4 years ago
I'm wondering if this is because of bug 939525?  (Though it was accessible about 1/2 hr ago, but is now not accessible.
colo-trip: --- → scl3
(Assignee)

Comment 2

4 years ago
This guy is a VM; it was up at the console.  Couldn't log in due to the keyrepeater problem.
Rebooted for that (:Callek ok'ed).

ifcfg-eth0 was set for dhcp, which Callek said it shouldn't be.  Cobbled in a static IP, then rebooted to make sure it sticks, and Callek has the ball now.

This looks to be internal-to-the-guest, IMO.  Something had to flip that file to DHCP inside the guest.
Assignee: server-ops-dcops → gcox
Status: NEW → RESOLVED
colo-trip: scl3 → ---
Last Resolved: 4 years ago
Component: Server Operations: DCOps → Server Operations
QA Contact: dmoore → shyam
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.