Unclear error when starting a node process when a port is already taken. #65
Comments
|
Thanks for the report! I believe this error was fixed in version 0.11.9 of the module -- it's an issue in one of the underlying libraries. What version of the module are you running? |
|
Was using 0.11.5 Thanks! |
|
Sweeet! 🎉 |
cmcadams-newrelic
pushed a commit
to cmcadams-newrelic/node-newrelic
that referenced
this issue
Jan 29, 2024
added simple inifinite trace mock server
jsumners-nr
pushed a commit
to jsumners-nr/node-newrelic
that referenced
this issue
Apr 11, 2024
removed methods lib and use our own implementation
jsumners-nr
pushed a commit
to jsumners-nr/node-newrelic
that referenced
this issue
Apr 16, 2024
…_updates Updates to Readme, guidelines and templates
bizob2828
pushed a commit
to bizob2828/node-newrelic
that referenced
this issue
Apr 19, 2024
…endency Remove AWS servers as dependency for versioned tests
bizob2828
pushed a commit
to bizob2828/node-newrelic
that referenced
this issue
Apr 23, 2024
…endency Remove AWS servers as dependency for versioned tests
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Without node-newrelic, when you attempt to start a server with a port take, then error message is similar to:
Error: listen EADDRINUSEWith node-newrelic, you get this:
TypeError: Cannot read property 'onconnection' of nullTook me a while to realize this meant I had a node server on the same port still running in another tab.
The text was updated successfully, but these errors were encountered: