Node 0.10.x - Port still in use after a "pm2 stop :id"

[stumpyfr]

When I kill a pm2 process (http server with expressjs) with the kill command and try to restart the same process without pm2 I get:

server started on port 4242
   warn  - error raised: Error: listen EADDRINUSE

events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: listen EADDRINUSE
    at errnoException (net.js:901:11)
    at Server._listen2 (net.js:1039:14)
    at listen (net.js:1061:10)
    at Server.listen (net.js:1127:5)

If I start the process with pm2, everything is working.

To be able to start the process without pm2, I need to kill the pm2 demon process: 'pm2: Satan Daemonizer'.

Not very practical :).

[Unitech]

I tried with node v0.8.17 and v0.11.2, everything is okay, the port is freed when a process is stopped.

The command to stop a process managed by pm2 is pm2 stop <pm2_id|script_name|all>. pm2 kill is only to kill pm2.

Which node version do you use ?

Thanks

[stumpyfr]

my mistake, It's was about pm2 stop ;) and not kill.
node version: 0.10.17

[Unitech]

I confirm there is a bug with node v0.10.x the port is not freed when stopping the process with pm2 stop.
With v0.8.x and v0.11.x there isn't this bug.
I will try to have a deeper look at it, thanks for reporting this issue

[mehulved]

We've seen this issue even with node 0.8 but can't consistently reproduce it. If I do, I'll report it. What would be the suggested logs/trace that you'd need so I can get them if I run into this bug again.

[purepear]

Having the same issue with 0.10.. I had to make my git push hook kill and start the pm2 daemon

[Marsup]

It happens everytime for me, I'm still on node 0.8.25.

[elf-pavlik]

@Unitech http://nodejs.org states: Current Version: v0.10.19
great if we could get read of this major bug on 0.10.x
pm2 kill on github webhooks makes no fun :(

[Unitech]

i haven't found any solution to fix that. I tried 4 differents ways and nothing work with 0.10.x...

The only solution will be in the next pm2 version, who include "fork mode", it will not wrap the code anymore and the cluster feature will be disabled :(

Hope everyone will switch to 0.11.x or that the 1.x node version will have the same engine for cluster than 0.11.x

[rlidwka]

i haven't found any solution to fix that.

At least one solution would be to clone cluster.js from v0.11.x source code and use it in v0.10.x (the same way as people use streams2 in v0.10.x with readable-stream fallback for v0.8.x).

It would be a pain to maintain it though, so it's easier for people to just switch to v0.11.x, it's only a few months from being stable anyway.

[elf-pavlik]

does pm2 play nicely with nvm?

can i use node v0.11.x to run pm2 but make it still use node v0.10.x for running scripts i want to manage with it?

[matejkramny]

You can get this to happen when you shut down node improperly. Its a node
error not pm2, although i feel that if pm2 shuts node down differently it
may solve the issue you have

Matej Kramny

On 12 Oct 2013, at 01:28 pm, "☮ elf Pavlik ☮" notifications@github.com
wrote:

does pm2 play nicely with nvm?

can i use node v0.11.x to run pm2 but make it still use node v0.10.x for
running scripts i want to manage with it?

—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/74#issuecomment-26196575
.

[Unitech]

@matejkramny I tried shut down process in different ways (disconnecting, suicide, kill...) nothing works, the port is still not freed.

@rlidwka you think it's possible ? I'm scarred that all this mechanism comes from C++ modules and not the cluster.js, I will have a look at it

@elf-pavlik as the "cluster mode" require your code, you can't use different node version

[rlidwka]

I'm scarred that all this mechanism comes from C++ modules and not the cluster.js, I will have a look at it

cluster.js doesn't even require any native modules, but base around process.send(message, fd) function which I believe is the same in 0.12, 0.10 and even 0.8. Can't be sure though.

[Unitech]

@rlidwka I tried to use the Node v0.11x cluster module for 0.10.x, without success

For Node v0.10.x the workaround is now to launch your script in "fork mode" by adding the -x parameter.
To beneficiate of the fork mode you have to install at least the 0.6.3 version of pm2

$ npm install -g pm2@latest

I've added a section "known bugs" in the README.md : https://github.com/Unitech/pm2#known-bugs

Thanks for reporting, closing