Sometimes Locks Socket/Port Until Killed

[jvanalst]

This is on Mac OS X v10.8.2, node v0.10.26 and pm2 -V 0.7.8.

Sometimes when restarting/deleting/stopping a web server process the port remains open and stuck in the CLOSE_WAIT state. The only way to free the port and restart your application is to kill the pm2 Satan Daemonizer. (either with pm2 kill or sudo kill ###)

As you can imagine, having to kill pm2 is not an ideal solution if you have more than one application running at a time.

Jeff

[cadorn]

I am running into same issue.

[soyuka]

same here

[Unitech]

It's due to issues related to the cluster module on 0.10.x - #74

[cadorn]

I am using fork mode.

[hustcer]

Same here.

[Unitech]

DONT USE cluster_mode with Node 0.10.x ! Only Node 0.11.X (0.11.14 prefered)

[vachanda]

I'm facing similar issue with PM2 version 1.1.2. Node version is 5.7.1.

We're using PM2 to power our node application behind nginx. PM2 is running in cluster mode. After each of out deployment we perform PM2 reload all operation to perform a zero downtime restart. But we find that PM2 still maintains some socket connections with close_wait state.