-
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
Will not start app in cluster mode on Windows Server 2008 #1408
Comments
We have been digging into this issue. What we have been running into is an error thrown down in node (v0.12.5) on a app that tried to spin up a mssql connection on a named instance. While not certain the our best lead is that mssql connections use udp to negotiate a port. Apparently there is still a bug in node cluster.js where udp connections don't close. If anyone has insight or can confirm this issue it may save someone a lot of heartache. |
P.S - Use PM2 with --no-daemon to get information piped to the console. |
The issue we’ve experienced seem to be related to our app trying to connect to a mssql named instance. Basically there is still a issue inside one of node’s core features with cluster.js where udp connections do not get closed properly. Connecting to a named instance used udp to request connection information. In our case the app would start up and appear to be working from the PM2 console but almost immediately. Currently we are running the in fork mode in the environments where we use a named instance for mssql. Other environments which we use a instance running on 1433 seem to work fine in cluster_mode. I hope this helps. I lost about 2 days tracking down this issue. Regards,
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Hello,
I am trying to use PM2 in cluster mode on a Windows Server 2008 R2 Standard 64-bit machine.
node v0.12.5 pm2 v0.14.2
pm2 start test.js starts the app successfully.
pm2 start test.js -i 2 or pm2 start test.js -i 0 does not.
I tried this fix with no success
#868
Thanks for your help with this issue.
The text was updated successfully, but these errors were encountered: