-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
cluster mode opens new shell for each fork #1749
Comments
Any update on this issue? I'm using fork mode for now, but in Prod I will need many instances in parallel. Still happening in pm2 v1.0.0, Node v5.5.0. |
+1 |
1 similar comment
+1 |
Still no fix? |
I have the same issue! any updates? I also, have multiple restarts which ends in a crash. the node index.js is working fine as well as the npm start |
+1 |
With @vmarchaud we are having a hard time to find a solution to this issue. Node.js on Windows seems to behave like that when you create a new detached process. If someone have a clue about that, please let us know. |
close this one in favor of #2182 |
starts 4 new node shell windows, which then of course reopen every time you save a file (if you watch for changes).
Doesn't matter if started via CLI or config.
Only solution is to use
--no-daemon
switch, but then you have to open another shell for monitoring.pm2 version
0.15.9
, Node4.2.1
, Windows 7.The text was updated successfully, but these errors were encountered: