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: rebooted by seabld Jun 26 00:00:01 cb-sea-miniosx01 reboot: SHUTDOWN_TIME: 1340694001 948989 Jun 26 00:00:02 cb-sea-miniosx01 mDNSResponder mDNSResponder-176.3 (Jun 17 2009 18:57:49): stopping I logged off manually, and now it's not responding to ssh.
This is a mini in scl1, so it will get tapped on the next scl1 trip.
Assignee: server-ops → server-ops-releng
colo-trip: --- → scl1
Component: Server Operations → Server Operations: RelEng
QA Contact: phong → arich
The relops guys are out for a few days, so moving this to dcops in the hopes that they can help out.
Assignee: jwatkins → server-ops
Component: Server Operations: RelEng → Server Operations: DCOps
QA Contact: arich → dmoore
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
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.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.