Replies: 2 comments 3 replies
-
Transferring to a discussion item as I don't think this is a debugpy problem. |
Beta Was this translation helpful? Give feedback.
1 reply
-
I've seen a similar problem on windows if I used port 5678. This item sounds the same: On windows (for me), something else is trying to use that same port at the same time. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Before creating a new issue, please check the FAQ to see if your question is answered there.
Environment data
Actual behavior
I am on a compute cluster that uses LSF and I launch an interactive job to get into a compute node. In that compute node, I start
debugpy
usingpython -m debugpy --listen 0.0.0.0:1326 --wait-for-client -c "print('hello')"
And the serve is waiting for the client. However, when I try to connect to the server using VSCode, I get ECONNREFUSED. When I inspect the logs using
python -m debugpy --log-to logs --listen 0.0.0.0:1326 --wait-for-client -c "print('hello')"
I see the following:debugpy.pydevd.2718046.log
debugpy.server-2718046.log
debugpy.adapter-2718050.log
Notably, I see two issues (and I don't know which one causes which or which one comes first etc.):
and
Expected behavior
This was working before on the cluster and now it doesn't. Probably something in the cluster config was changed, but I would like to have some guidance on how to fix it/some understanding what could be going on.
Steps to reproduce:
I am trying to reproduce on a different cluster right now, but it might take a while as it is very busy.
Beta Was this translation helpful? Give feedback.
All reactions