New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 714252 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 714259
Owner:
Last visit > 30 days ago
Closed: Jun 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

kevin-paladin: closed connection and DNS failure

Project Member Reported by nxia@chromium.org, Apr 21 2017

Issue description

https://luci-milo.appspot.com/buildbot/chromeos/kevin-paladin/873

http://cautotest.corp.google.com/afe/#tab_id=view_job&object_id=113664538



04/21 08:30:28.148 ERROR|        base_utils:0280| [stderr] ssh: Could not resolve hostname chromeos2-row8-rack9-host21: Name or service not known
04/21 08:30:28.151 DEBUG|          ssh_host:0206| retrying ssh because of DNS failure
 

Comment 1 Deleted

Comment 2 Deleted

Comment 3 by nxia@chromium.org, Apr 21 2017

Another test failure in the same  kevin-paladin build. Connection to the dut was broken and DNS failure was showed on the log.


http://cautotest.corp.google.com/afe/#tab_id=view_job&object_id=113664502


https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/113664502-chromeos-test/chromeos2-row8-rack8-host2/debug


04/21 08:33:25.254 INFO |      abstract_ssh:0795| Master ssh connection to chromeos2-row8-rack8-host2 is down.
04/21 08:33:25.254 DEBUG|      abstract_ssh:0756| Nuking master_ssh_job.
04/21 08:33:25.255 DEBUG|      abstract_ssh:0762| Cleaning master_ssh_tempdir.
04/21 08:33:25.256 INFO |      abstract_ssh:0809| Starting master ssh connection '/usr/bin/ssh -a -x   -N -o ControlMaster=yes -o ControlPath=/tmp/_autotmp_iqAQJjssh-master/socket -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o BatchMode=yes -o ConnectTimeout=30 -o ServerAliveInterval=900 -o ServerAliveCountMax=3 -o ConnectionAttempts=4 -o Protocol=2 -l root -p 22 chromeos2-row8-rack8-host2'
04/21 08:33:25.256 DEBUG|        base_utils:0185| Running '/usr/bin/ssh -a -x   -N -o ControlMaster=yes -o ControlPath=/tmp/_autotmp_iqAQJjssh-master/socket -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o BatchMode=yes -o ConnectTimeout=30 -o ServerAliveInterval=900 -o ServerAliveCountMax=3 -o ConnectionAttempts=4 -o Protocol=2 -l root -p 22 chromeos2-row8-rack8-host2'
04/21 08:33:30.392 INFO |      abstract_ssh:0824| Timed out waiting for master-ssh connection to be established.
04/21 08:33:30.394 DEBUG|      abstract_ssh:0357| Using Rsync.
04/21 08:33:30.395 DEBUG|        base_utils:0185| Running 'rsync -l  --timeout=1800 --rsh='/usr/bin/ssh -a -x   -o ControlPath=/tmp/_autotmp_iqAQJjssh-master/socket -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o BatchMode=yes -o ConnectTimeout=30 -o ServerAliveInterval=900 -o ServerAliveCountMax=3 -o ConnectionAttempts=4 -o Protocol=2 -l root -p 22' -az --no-o --no-g root@chromeos2-row8-rack8-host2:"/usr/local/autotest/results/default/" "/usr/local/autotest/results/113664502-chromeos-test/chromeos2-row8-rack8-host2"'
04/21 08:36:24.316 WARNI|      abstract_ssh:0387| trying scp, rsync failed: Command <rsync -l  --timeout=1800 --rsh='/usr/bin/ssh -a -x   -o ControlPath=/tmp/_autotmp_iqAQJjssh-master/socket -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o BatchMode=yes -o ConnectTimeout=30 -o ServerAliveInterval=900 -o ServerAliveCountMax=3 -o ConnectionAttempts=4 -o Protocol=2 -l root -p 22' -az --no-o --no-g root@chromeos2-row8-rack8-host2:"/usr/local/autotest/results/default/" "/usr/local/autotest/results/113664502-chromeos-test/chromeos2-row8-rack8-host2"> failed, rc=255, Command returned non-zero exit status
* Command: 
    rsync -l  --timeout=1800 --rsh='/usr/bin/ssh -a -x   -o ControlPath=/tmp
    /_autotmp_iqAQJjssh-master/socket -o StrictHostKeyChecking=no -o
    UserKnownHostsFile=/dev/null -o BatchMode=yes -o ConnectTimeout=30 -o
    ServerAliveInterval=900 -o ServerAliveCountMax=3 -o ConnectionAttempts=4
    -o Protocol=2 -l root -p 22' -az --no-o --no-g
    root@chromeos2-row8-rack8-host2:"/usr/local/autotest/results/default/"
    "/usr/local/autotest/results/113664502-chromeos-
    test/chromeos2-row8-rack8-host2"
Exit status: 255
Duration: 173.809476137

stderr:
ssh: Could not resolve hostname chromeos2-row8-rack8-host2: Name or service not known
rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]

Comment 4 by nxia@chromium.org, Apr 21 2017

Summary: kevin-paladin: closed connection and DNS failure (was: kevin-paladin platform_FilePerms: DNS failure )

Comment 5 by nxia@chromium.org, Apr 21 2017

Cc: owenlin@chromium.org tbroch@chromium.org zhihongyu@chromium.org
Labels: -Pri-2 Pri-1

Comment 6 by aut...@google.com, Apr 25 2017

Owner: nxia@chromium.org
network outage root cause, nxia to de-dupe

Comment 7 by nxia@chromium.org, Jun 20 2017

Mergedinto: 714259
Status: Duplicate (was: Untriaged)

Sign in to add a comment