Replies: 1 comment
-
Adding It would be nice to have this documented somewhere (setup and teardown of the single native client). |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi everyone, need some help with an issue I'm seeing with a particular host. This host is remotely power cycled and I am using ParallelSSH to probe its status and execute commands on it. This host is running
Ubuntu 22.04.4 LTS (GNU/Linux 5.17.11spm x86_64)
and its openssl version isOpenSSL 3.0.2 15 Mar 2022 (Library: OpenSSL 3.0.2 15 Mar 2022)
. My Python script is running in a Docker container from the "ubuntu:22.04" base image with the same version of openssl (OpenSSL 3.0.2 15 Mar 2022 (Library: OpenSSL 3.0.2 15 Mar 2022)
).Note: the reason I'm using the
close_channel()
function below is because through trial and error (specifically with this host), it has allowed me to get deterministic behaviour out of it, especially during power cycles where connection is disrupted and strange behaviours are observed. As a side question, I would like to know what the proper way of "cleaning up" the connection in cases like these, where the socket is expected to get forcibly disconnected.In the current implementation, a host is power cycled and it is polled to determine if it's ready to accept SSH commands. Here is that code:
This is looped until we receive a response and works as intended:
However, subsequent commands are failing. And logs are revealing that no password has been provided.
Here's the next chunk of code dispatching commands after the server poll:
Here's the resulting log:
I have confirmed that I am passing it the same credentials. Is there something I'm doing that is preventing the password from being provided?
Beta Was this translation helpful? Give feedback.
All reactions