Debugger stuck on connecting then throws ETIMEDOUT

[acostaf]

I follow instruction from https://github.com/angular/protractor/blob/master/docs/debugging.md
however the prompt get stuck on connecting

C:\Users\user\IAMT\trunk\net\project\Tests>protractor debug protractor.config.js
< debugger listening on port 5858
connecting......

then after 5 mins I get this

connecting.............There was an internal error in Node's debugger. Please report this bug.
connect ETIMEDOUT
Error: connect ETIMEDOUT
at errnoException (net.js:901:11)
at Object.afterConnect as oncomplete

[juliemr]

Possibly a windows issue? I've never seen this. Filing as needs more investigation.

[acostaf]

indeed I am using windows, with latest version of everything

[fabiosussetto]

I'm getting the same issue on OSX too, using the latest versions of everything.

[fabiosussetto]

After some investigation, I managed to fix the issue thanks to this: https://github.com/ajaxorg/cloud9/issues/2170

Basically, it seems that I had another node process in the background. After running $ pkill -f node (or just $ kill -9 ) I can run the debugger again.

[asherrard]

was gettting this same issue on OSX after I switched from using a local npm version of protractor to a globally installed version. running $ pkill -f node fixed this allowed me to connect however I could not get a protractor test to run. Side note, once I switched to a global version protractor I started seeing, I wasnt seeing that before
< ------------------------------------
< PID: 10244 (capability: chrome #1)
< ------------------------------------
< debugger listening on port 5858

[vlouppe]

Thanks fabiosussetto. It was the solution to my problem.

[fabiosussetto]

I think there are still some issues for the debugger though.
If I try to run my tests in debug mode, with this command:

$ node_modules/protractor/bin/protractor debug tests/conf.js

The first output I get is:

break in node_modules/protractor/lib/cli.js:7

which seems to be an internal breakpoint in protractor's source code.

Then if I try to press "c" or "n" to let the debugger carry on to the actual breakpoint in one of my tests, nothing happens. I just get again "debugger listening on port 5858" with the debugging cli waiting.

[juliemr]

@fabiosussetto I think you're seeing #552.

You will always get an automatic breakpoint at the start of code with the node debugger - it's not an internal protractor thing.

[juliemr]

Issues with #552 fixed with the latest release! Closing.