Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix "Connection closed by remote host" error on Google Cloud ssh #5069

Closed
teor2345 opened this issue Sep 5, 2022 · 8 comments · Fixed by #5330 or #5602
Closed

Fix "Connection closed by remote host" error on Google Cloud ssh #5069

teor2345 opened this issue Sep 5, 2022 · 8 comments · Fixed by #5330 or #5602
Assignees
Labels
A-devops Area: Pipelines, CI/CD and Dockerfiles C-bug Category: This is a bug I-integration-fail Continuous integration fails, including build and test failures

Comments

@teor2345
Copy link
Contributor

teor2345 commented Sep 5, 2022

Motivation

A few different PRs seem to be failing with this error:

kex_exchange_identification: Connection closed by remote host
https://github.com/ZcashFoundation/zebra/runs/8161163434?check_suite_focus=true#step:7:86

@teor2345 teor2345 added C-bug Category: This is a bug A-devops Area: Pipelines, CI/CD and Dockerfiles S-needs-triage Status: A bug report needs triage P-High 🔥 I-integration-fail Continuous integration fails, including build and test failures labels Sep 5, 2022
@teor2345
Copy link
Contributor Author

teor2345 commented Sep 7, 2022

I haven't seen these errors recently, I wonder if they are caused by rate-limiting?

We could add the ConnectionAttempts option to the SSH command-line to fix this.

@teor2345
Copy link
Contributor Author

@teor2345
Copy link
Contributor Author

@teor2345
Copy link
Contributor Author

It looks like this is now more frequent than the other Google Cloud errors.

@mergify mergify bot closed this as completed in #5330 Oct 5, 2022
Repository owner moved this from 📋 Sprint Backlog to ✅ Done in Zebra Oct 5, 2022
@gustavovalverde
Copy link
Member

gustavovalverde commented Oct 31, 2022

The main branch has been failing recently with this errors. So I'm reopening this one

@gustavovalverde
Copy link
Member

I've been able to find this error log in GCP

Supplied fingerprint does not match current metadata fingerprint.

I've also found the root cause: some ssh-keys in the project metadata that might have been added when testing OS Login.

This might not solve the problem, but will at least reduce the noise when searching for the actual error.

@teor2345
Copy link
Contributor Author

teor2345 commented Nov 3, 2022

I've also found the root cause: some ssh-keys in the project metadata that might have been added when testing OS Login.

Thanks for tracking this down!

@mpguerra mpguerra moved this from ✅ Done to 🆕 New in Zebra Nov 9, 2022
@mergify mergify bot closed this as completed in #5602 Nov 16, 2022
Repository owner moved this from 🆕 New to ✅ Done in Zebra Nov 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-devops Area: Pipelines, CI/CD and Dockerfiles C-bug Category: This is a bug I-integration-fail Continuous integration fails, including build and test failures
Projects
Archived in project
3 participants