-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reproducible: Error: listen EADDRINUSE :::3000 #1484
Comments
|
This setup is so verbose because I took our project and simplified it for reproducibility as much as was a bit easy. I'd like to see how reproducible this actually is on other systems. |
Same behaviour here, nodemon crashes with |
@sofiia-hlyniana this is a docker + nodemon issue. Are you saying you're seeing the same? |
@remy Sorry, didn't notice docker was also there. I'm not using it, but I see the same error as described using nodemon only. However, I still can create another issue if it is critical to do so. |
@sofiia-hlyniana no problem. If you can, and if you can include code that can replicate the problem then it makes it marginally easier to debug 👍 |
Also running into this error, after upgrading |
Also have this issue after recent upgrade. |
We're also seeing this issue when using Docker. We're using nodemon v1.18.7. |
Experiencing this issue also, nodemon v1.18.7 |
This was previously working fine on v1.17.2. However after upgrading to v1.18.7, this issue started happening. Tried to downgrade again to v1.17.2, it was not enough - the bug was still present. It seems that the Using v1.17.2, and adding the following workaround in "resolutions": {
"nodemon/pstree.remy": "1.1.0"
} |
@avaly thanks! that works |
How does one do this for |
@servel333 just add the that snippet to your |
That is a duplicated of #1477 which is being discussed already and we are trying to find the fix. |
@servel333 the solution works only with |
I also confirmed that using |
I also confirm that using |
@zefexdeveloper Some people in this thread have said they can reproduce this without Docker. Does that still make this a duplicate? |
@servel333 I came to the same root cause |
@servel333 Judging by the main subject, yes, it's duplicated, people saying that they are having the same issue without Docker is just a consequence, but anyway, we are just trying to find a solution anyway 😄 |
This is splitting hairs, but technically my subject doesn't mention Docker... @zefexdeveloper :) |
|
I've been working on this today. The problem is in the ps tree implementation I took from node-kill-tree - basically it doesn't work across all docker images. I'm refactoring the pstree.remy so that it will work. It's because ps and how processes are killed, work slightly differently in the alpine flavour of linux. |
Live fix in nodemon@1.18.8 (core change in pstree.remy…again). |
Still having the same issue with 1.1.8 in |
also with |
@timini are you able to debug? |
Seems to work with |
@remy What do you want to know? It seems the |
Ideally what to change to fix it. |
Can you give me a clue where to start looking? Bearing in mind I have no existing knowledge of the pstree package |
Equally I have know existing knowledge as to the specifics of your dev environment…you've not provided any example code to replicate with so there's no real point in trying to guess. pstree package is very small: https://github.com/remy/pstree/blob/master/lib/index.js But you're going to have a better idea if you look at nodemon's source in |
nodemon -v
: 1.17.3node -v
: v9.11.2Darwin Kernel Version 17.7.0: Thu Jun 21 22:53:14 PDT 2018; root:xnu-4570.71.2~1/RELEASE_X86_64
)Expected behaviour
Actual behaviour
Steps to reproduce
make start-test
If applicable, please append the
--dump
flag on your command and include the output here ensuring to remove any sensitive/personal details or tokens.The text was updated successfully, but these errors were encountered: