Numerous ssh errors from shard to devserver |
||
Issue descriptionExample provision sshing from chromeos-server98 to chromeos4-devserver1/100.115.219.129: https://storage.cloud.google.com/chromeos-autotest-results/hosts/chromeos4-row11-rack11-host9/2326631-provision/20171912000341/provision_AutoUpdate/debug/provision_AutoUpdate.DEBUG?_ga=2.221996440.-1609996729.1510708542 Many errors of the form: 12/19 00:11:36.428 DEBUG| utils:0212| Running 'ssh 100.115.219.129 'curl "http://100.115.219.129:8082/get_au_status?full_update=False&force_update=True&pid=19523&build_name=cyan-paladin/R65-10228.0.0-rc3&quick_provision=True&host_name=chromeos4-row11-rack11-host9&clobber_stateful=True"'' 12/19 00:11:36.597 DEBUG| dev_server:0936| Error occurred with exit_code 255 when executing the ssh call: ssh_exchange_identification: Connection closed by remote host These particular errors are recovered by the system, but given the frequency, I'm guessing they occasionally translate into actual failures and should be understood. They also appear somewhat transient and aren't always occurring. Things to investigate: - is it source/destination that has the issue - packet dumps of when failures occur - relevant logs on the ssh server side
,
Jan 4 2018
Quite a few things could cause that. It could be connection limits of some kind, authentication errors, etc. Looking for matching logs on the devserver might be revealing.
,
Jan 7
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||
►
Sign in to add a comment |
||
Comment 1 by ayatane@chromium.org
, Dec 27 2017Status: Available (was: Untriaged)