768346 - cb-sea-miniosx01 isn't back from a reboot.

Status: RESOLVED FIXED

(Infrastructure & Operations :: DCOps, task)

Description

[Edmund Wong (:ewong)]

cb-sea-miniosx01 was noted as being disconnected from the master.
SSH'd in, and sudo reboot.  (It didn't log me off, which is strange for a
machine that's supposed to reboot.)

Jun 26 00:00:01 cb-sea-miniosx01 reboot[352]: rebooted by seabld
Jun 26 00:00:01 cb-sea-miniosx01 reboot[352]: SHUTDOWN_TIME: 1340694001 948989
Jun 26 00:00:02 cb-sea-miniosx01 mDNSResponder mDNSResponder-176.3 (Jun 17 2009
18:57:49)[16]: stopping

I logged off manually, and now it's not responding to ssh.

Comment 1

[Dustin J. Mitchell [:dustin] (he/him)]

This is a mini in scl1, so it will get tapped on the next scl1 trip.

Comment 2

[Amy Rich [:arr] [:arich]]

The relops guys are out for a few days, so moving this to dcops in the hopes that they can help out.

Comment 3

[Van Le [:van]]

the host originally had the ethernet port disabled. i wasnt able to manually reenable it so i rebooted the host. the host is back up with the ethernet port enabled. i am unable to ping the host from the admin host or the jumphost. but from within the host, i am able to ping it's gateway (10.12.20.1).

let me know what else i can do to help.

thanks,
van

Comment 4

[Dustin J. Mitchell [:dustin] (he/him)]

I'm a dummy - those shouldn't be pingable from jump1.community.scl3.  They're accessible via jump1.comm-build.scl1, so this is done.