Home › Forums › FABRIC General Questions and Discussion › node.execute() hangs in FABRIC notebook
- This topic has 8 replies, 3 voices, and was last updated 6 days, 6 hours ago by
Fatih Berkay Sarpkaya.
-
AuthorPosts
-
February 18, 2026 at 11:08 am #9516
Dear FABRIC team,
I hope you are doing well. In my FABRIC notebook, when I run commands on nodes using node.execute(), the command sometimes works normally, but other times it just hangs indefinitely without returning any error. The node itself remains reachable via SSH, and the same command runs immediately from the terminal. I have tried restarting the notebook server, but the issue persists. Do you have any suggestions on how to solve this problem?
Thank you.
Best regards,
Fatih Berkay Sarpkaya
February 18, 2026 at 11:10 am #9517Hi Fatih,
Could you please check if you see any errors in the
/tmp/fablib/fablib.log?Also, could you please share which Jupyter Container are you using?
Best,
Komal
February 18, 2026 at 11:21 am #9518Hi Komal,
Thank you for your reply. I checked /tmp/fablib/fablib.log, and I see the following errors:
[15:51:05] {/opt/conda/lib/python3.11/site-packages/paramiko/transport.py:1938} ERROR – Secsh channel 0 open FAILED: Connection timed out: Connect failed
[15:51:05] {/opt/conda/lib/python3.11/site-packages/fabrictestbed_extensions/fablib/node.py:1665} WARNING – Attempt 1 failed: ChannelException(2, ‘Connect failed’)
[15:54:47] {/opt/conda/lib/python3.11/site-packages/paramiko/transport.py:1938} ERROR – Secsh channel 0 open FAILED: Connection timed out: Connect failed
[15:54:47] {/opt/conda/lib/python3.11/site-packages/fabrictestbed_extensions/fablib/node.py:1665} WARNING – Attempt 1 failed: ChannelException(2, ‘Connect failed’)
[16:05:26] {/opt/conda/lib/python3.11/site-packages/paramiko/transport.py:1938} ERROR – Secsh channel 0 open FAILED: Connection timed out: Connect failed
[16:05:26] {/opt/conda/lib/python3.11/site-packages/fabrictestbed_extensions/fablib/node.py:1665} WARNING – Attempt 1 failed: ChannelException(2, ‘Connect failed’)
[16:09:07] {/opt/conda/lib/python3.11/site-packages/paramiko/transport.py:1938} ERROR – Secsh channel 0 open FAILED: Connection timed out: Connect failed
[16:09:07] {/opt/conda/lib/python3.11/site-packages/fabrictestbed_extensions/fablib/node.py:1665} WARNING – Attempt 1 failed: ChannelException(2, ‘Connect failed’)
[16:11:26] {/opt/conda/lib/python3.11/site-packages/paramiko/transport.py:1938} ERROR – Secsh channel 0 open FAILED: Connection timed out: Connect failed
[16:11:26] {/opt/conda/lib/python3.11/site-packages/fabrictestbed_extensions/fablib/node.py:1665} WARNING – Attempt 2 failed: ChannelException(2, ‘Connect failed’)My Jupyter container is: kthare10/jupyter-notebook:1.9.2r2
Best regards,
Fatih Berkay Sarpkaya
February 18, 2026 at 11:32 am #9519Hi Fatih,
Could you please try changing the following files:
/home/fabric/work/fabric_config/ssh_config/home/fabric/work/fabric_config/fabric_configchange
bastion.fabric-testbed.nettobastion-ncsa-1.fabric-testbed.netin both the files.Reload the kernel of your notebook and try the
node.executeThanks,
Komal
February 18, 2026 at 11:44 am #9520Hi Komal,
It seems to be working now. Thank you very much for your help.
Best regards,
Fatih Berkay Sarpkaya
February 25, 2026 at 8:17 am #9533May I ask which OS is running on your nodes?. We are trying to narrow down the issue.
February 25, 2026 at 9:22 am #9534Hi,
The nodes are running Ubuntu 22.04.5 LTS.
Thank you.
Best regards,
Fatih Berkay Sarpkaya
February 25, 2026 at 9:38 am #9535Which SITE was this VM on ? Also, could you please share the notebook you used when you encountered the issue? you can email the notebook to help@fabric-testbed.net.
February 25, 2026 at 3:05 pm #9546Hi,
At this point, I am no longer experiencing the issue after applying the modification mentioned in this thread. However, when I initially encountered the problem, I was testing a slice at the SRI site. I will email the relevant portion of the notebook I used to help@fabric-testbed.net shortly.
Best regards,
Fatih Berkay Sarpkaya
-
AuthorPosts
- You must be logged in to reply to this topic.