Unable to access cb-xserve01

RESOLVED FIXED

Status

--
major
RESOLVED FIXED
9 years ago
4 years ago

People

(Reporter: samuel.sidler+old, Assigned: phong)

Tracking

Details

In bug 513718, cb-xserve01 was re-imaged, apparently based on cb-xserve03. Unfortunately, this machine should be setup for Camino, which should use the "caminobld" user name and the password we use for that account (I can PM an IT person on IRC with that password).

I also noticed that, when pinging the machine, it pings cg-xserve01 and the pings timeout.

  [ss@cb-jumphost01 ~]$ ping cb-xserve01.mozilla.com
  PING cg-xserve01.mozilla.com (63.245.210.11) 56(84) bytes of data.

That doesn't seem quite right...

I really want to make this bug "critical" since it stops us from setting the machine back up, but I'll leave it as "major" since it's for a Camino box...
Phong, can you take a look at this?
I've got the auth info for cb-xserve03 so I'll fix up cb-xserve01.
Assignee: server-ops → nthomas
Status: NEW → ASSIGNED
Can't get VNC to respond and have no KVM setup here so back to Server Ops. FWIW, it's setup with a calbld account at the moment as cb-serve03 was a Calendar box. 

To do: Hostname needs setting to cb-xerve01; add caminobld user with appropriate p/w (ask ss), enable VNC and set p/w to same; remove calbld user and it's home dir.

The cb-xserve01 vs cg-xserve01 thing is just a DNS alias
[nthomas@cb-jumphost01 ~]$ host cb-xserve01.mozilla.com
cb-xserve01.mozilla.com is an alias for cg-xserve01.mozilla.com.
cg-xserve01.mozilla.com has address 63.245.210.11
IIRC community build (cb) predates community giving (cg).
Assignee: nthomas → server-ops
Status: ASSIGNED → NEW
(Assignee)

Updated

9 years ago
Assignee: server-ops → phong
Flags: colo-trip+
(Assignee)

Comment 4

9 years ago
password updated with the current caminobld password from SS.
Looks good! Thanks!
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.