Home › Forums › FABRIC General Questions and Discussion › SSH Connection Error: ChannelException(2, ‘Connect failed’)
- This topic has 4 replies, 2 voices, and was last updated 4 days, 15 hours ago by Komal Thareja.
-
AuthorPosts
-
January 16, 2025 at 3:35 pm #8075
Summary of the Issue:
I attempted to run the following command on the worker node using the
worker1.execute()
function:sudo apt update && sudo apt install -y net-tools && pip install netifaces
However, the operation failed with the following error message:
paramiko.ssh_exception.ChannelException: ChannelException(2, ‘Connect failed’)
Error Details from Logs:
[14:36:51] {/home/johnnydai/miniconda3/lib/python3.11/site-packages/paramiko/transport.py:1909} ERROR – Secsh channel 0 open FAILED: No route to host: Connect failed
[14:36:51] {/home/johnnydai/miniconda3/lib/python3.11/site-packages/fabrictestbed_extensions/fablib/node.py:1644} WARNING – Exception in node.execute() command: sudo apt update && sudo apt install -y net-tools && pip install netifaces (attempt #0 of 3): ChannelException(2, ‘Connect failed’)
[14:37:05] {/home/johnnydai/miniconda3/lib/python3.11/site-packages/paramiko/transport.py:1909} ERROR – Secsh channel 0 open FAILED: No route to host: Connect failed
[14:37:05] {/home/johnnydai/miniconda3/lib/python3.11/site-packages/fabrictestbed_extensions/fablib/node.py:1644} WARNING – Exception in node.execute() command: sudo apt update && sudo apt install -y net-tools && pip install netifaces (attempt #1 of 3): ChannelException(2, ‘Connect failed’)
[14:37:19] {/home/johnnydai/miniconda3/lib/python3.11/site-packages/paramiko/transport.py:1909} ERROR – Secsh channel 0 open FAILED: No route to host: Connect failed
[14:37:19] {/home/johnnydai/miniconda3/lib/python3.11/site-packages/fabrictestbed_extensions/fablib/node.py:1644} WARNING – Exception in node.execute() command: sudo apt update && sudo apt install -y net-tools && pip install netifaces (attempt #2 of 3): ChannelException(2, ‘Connect failed’)January 16, 2025 at 3:38 pm #8076Hi Yuanjun,
Both the issues with upload_file and this point to SSH access to the VMs. It could be because of the expired bastion keys or a configuration issue.
Is it possible for a quick zoom meeting to resolve this? Please let me know if that works.Thanks,
KomalJanuary 16, 2025 at 3:40 pm #8077Hi,
Yes. We can have a quick zoom meeting to deal with the problems. Please contact yxd429@case.edu.
Thank you !
January 16, 2025 at 3:46 pm #8078The upload _file API works now.
To my case,I can use the bastion key to login in the VMs. It seems the bastion keys does not expire.
Some of the VMs does not have problem to run the execute command but some VMs have such problem.
I use the same code and it never happen before the new update.
Best Regards,
January 17, 2025 at 9:03 am #8084User has confirmed that this is no longer an issue.
HI, KomalThe problem has been solved. I believe we do not need the meeting today.
Thank you so much for your help!
Best Regards,
Yuanjun Dai
-
AuthorPosts
- You must be logged in to reply to this topic.