-
Notifications
You must be signed in to change notification settings - Fork 208
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
SSH Transport: Channel seems to be in a superposition of open and closed #4940
Labels
Comments
About the SSH setup: key comes from token/agent, but it remains in the cache for a long time. |
and possibly related I got the following warning at some point:
|
Simply replaying the tasks did not help as they repeatedly ended up in the same state again with the same error message. |
dev-zero
added a commit
that referenced
this issue
Jul 19, 2021
SSH provides multiple ways to forward connections. The legacy way is via SSHProxyCommand which spawns a separate process for each jump host/proxy. Controlling those processes is error prone and lingering/hanging processes have been observed (#4940 and others, depending on the setup). This commit adds support for the SSHProxyJump feature which permits to setup an arbitrary number of proxy jumps without additional processes by creating TCP channels over existing (Paramiko) connections. This gives a good control over the lifetime of the different connections and since a users SSH config is not re-read after the initial setup gives a controlled environment. Hence it has been decided to make this new directive the recommended default in the documentation while still supporting both ways. Co-authored-by: Marnik Bercx <mbercx@gmail.com> Co-authored-by: Leopold Talirz <leopold.talirz@gmail.com>
sphuber
pushed a commit
that referenced
this issue
Aug 8, 2021
SSH provides multiple ways to forward connections. The legacy way is via SSHProxyCommand which spawns a separate process for each jump host/proxy. Controlling those processes is error prone and lingering/hanging processes have been observed (#4940 and others, depending on the setup). This commit adds support for the SSHProxyJump feature which permits to setup an arbitrary number of proxy jumps without additional processes by creating TCP channels over existing (Paramiko) connections. This gives a good control over the lifetime of the different connections and since a users SSH config is not re-read after the initial setup gives a controlled environment. Hence it has been decided to make this new directive the recommended default in the documentation while still supporting both ways. Co-authored-by: Marnik Bercx <mbercx@gmail.com> Co-authored-by: Leopold Talirz <leopold.talirz@gmail.com> Cherry-pick: da179dc
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
After launching a couple of hundred workchains by demon (which in turn launches a number of calculations per workchain), I get for ~10% of the uploads this error:
and with
verdi process report
:Your environment
The text was updated successfully, but these errors were encountered: