Closed Bug 1498997 Opened 6 years ago Closed 6 years ago

[MDC1] t-yosemite-r7-367 not reachable

Categories

(Infrastructure & Operations :: RelOps: General, task)

Product:
Infrastructure & Operations
Component:
RelOps: General
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: apop, Assigned: dhouse)

References

Details

Tried to log on the machine this morning, but I've received the following error : Stdio forwarding request failed: Session open refused by peer ssh_exchange_identification: Connection closed by remote host Also, by checking the papertrail logs, I've only found the following line : Oct 15 00:55:33 rejh1.srv.releng.mdc1.mozilla.com sshd: error: connect_to t-yosemite-r7-367.test.releng.mdc1.mozilla.com port 22: failed. On taskcluster is missing. Can you please take a look ?
Blocks: t-yosemite-r7-367
Assignee: relops → dhouse
Summary: [MDC1] t-yosemite-r7-367 stdio issue → [MDC1] t-yosemite-r7-367 not reachable
no response to ping or ssh nothing in papertrail https://papertrailapp.com/groups/1141234?filter=t-yosemite-r7-367 ``` [dhouse@rejh2.srv.releng.mdc1.mozilla.com relops-infra]$ ping -c1 t-yosemite-r7-367.test.releng.mdc1.mozilla.com; ssh -vv root@t-yosemite-r7-367.test.releng.mdc1.mozilla.com PING t-yosemite-r7-367.test.releng.mdc1.mozilla.com (10.49.56.151) 56(84) bytes of data. --- t-yosemite-r7-367.test.releng.mdc1.mozilla.com ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 10000ms OpenSSH_6.6, OpenSSL 1.0.1e-fips 11 Feb 2013 debug1: Reading configuration data /home/dhouse/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 4: Applying options for * debug2: ssh_connect: needpriv 0 debug1: Connecting to t-yosemite-r7-367.test.releng.mdc1.mozilla.com [10.49.56.151] port 22. debug1: connect to address 10.49.56.151 port 22: Connection timed out ssh: connect to host t-yosemite-r7-367.test.releng.mdc1.mozilla.com port 22: Connection timed out ``` I turned on the pdu power and then back on manually, and still no response to ping or ssh. ``` # snmpget -v 2c -c public pdu1.rit40.ops.releng.mdc1.mozilla.com 1.3.6.1.4.1.1718.3.2.3.1.5.1.1.13 iso.3.6.1.4.1.1718.3.2.3.1.5.1.1.13 = INTEGER: 1 # snmpset -v 2c -c secret pdu1.rit40.ops.releng.mdc1.mozilla.com 1.3.6.1.4.1.1718.3.2.3.1.11.1.1.13 i 2 iso.3.6.1.4.1.1718.3.2.3.1.11.1.1.13 = INTEGER: 2 # snmpget -v 2c -c public pdu1.rit40.ops.releng.mdc1.mozilla.com 1.3.6.1.4.1.1718.3.2.3.1.5.1.1.13 iso.3.6.1.4.1.1718.3.2.3.1.5.1.1.13 = INTEGER: 0 # snmpset -v 2c -c secret pdu1.rit40.ops.releng.mdc1.mozilla.com 1.3.6.1.4.1.1718.3.2.3.1.11.1.1.13 i 1 iso.3.6.1.4.1.1718.3.2.3.1.11.1.1.13 = INTEGER: 1 # snmpget -v 2c -c public pdu1.rit40.ops.releng.mdc1.mozilla.com 1.3.6.1.4.1.1718.3.2.3.1.5.1.1.13 iso.3.6.1.4.1.1718.3.2.3.1.5.1.1.13 = INTEGER: 1 ``` ``` [dhouse@rejh2.srv.releng.mdc1.mozilla.com relops-infra]$ ping -c1 t-yosemite-r7-367.test.releng.mdc1.mozilla.com; ssh -vv root@t-yosemite-r7-367.test.releng.mdc1.mozilla.com PING t-yosemite-r7-367.test.releng.mdc1.mozilla.com (10.49.56.151) 56(84) bytes of data. --- t-yosemite-r7-367.test.releng.mdc1.mozilla.com ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 10000ms OpenSSH_6.6, OpenSSL 1.0.1e-fips 11 Feb 2013 debug1: Reading configuration data /home/dhouse/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 4: Applying options for * debug2: ssh_connect: needpriv 0 debug1: Connecting to t-yosemite-r7-367.test.releng.mdc1.mozilla.com [10.49.56.151] port 22. debug1: connect to address 10.49.56.151 port 22: Connection timed out ssh: connect to host t-yosemite-r7-367.test.releng.mdc1.mozilla.com port 22: Connection timed out ```
Opened case with QTS to reboot and check the machine: RITM0264843
completed reboot and the machine looks good
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.