Windows support #6

Volox opened this Issue Jun 14, 2013 · 13 comments

9 participants


Running on windows i keep seeing Launching daemon but nothing happens.
I tried with the json file and manually with pm2 start app.js but with no luck.
Also pm2 list and the other commands give the same result.
I am doing something wrong?


OS: Win 7 x64
node: 0.10.3


Hello, thanks for reporting issues.

PM2 is a production module, who should be mainly used on Linux servers. I haven't tried it on other platforms than Linux.

Feel free to contribute if you want to integrate this compatibility feature !



When changed detached: true to false in Satan.launchDaemon daemon forking options got this error:

        throw er; // Unhandled 'error' event
Error: spawn Unknown system errno 203
    at errnoException (child_process.js:945:11)
    at Process.ChildProcess._handle.onexit (child_process.js:736:34)

but cant find what is that 203 error.


how about use nssm in windows? there is another project:


I was trying to get pm2 to work on my Windows-based development workstation for testing purposes, but whenever I invoke it with any parameters, I get:

        throw arguments[1]; // Unhandled 'error' event
Error: connect EADDRNOTAVAIL
    at errnoException (net.js:770:11)
    at Object.afterConnect [as oncomplete] (net.js:761:19)

I tried debugging pm2, but I really didn't get anywhere. What is the execution path after everything in the pm2 file is defined?

@Unitech Unitech closed this Jul 28, 2014

We just launched a crowd funding campaign on boutysource for the Windows support:

Hope we will get enough attention for this Windows feature !


Could you try the Windows support:

C:/ $ npm install git:// -g

Give us your feedback!


@Unitech Well, it starts our application. Which is more than what I got on the first try with pm2 on Windows ;)


Good (: Apparently I got a feedback about the PID that is not refreshed on restart ( #777 ) Do you have the same bug?



I'll have to properly test at work during the week and I really have to get more into the specifics of pm2. I'll post if I trip over anything.


@oliversalzburg Thanks! Windows tester are not easy to find these days! (don't ask why...)


I have the same problem on widows server.


I also still have this problem, also after installing the development branch


Try setting PM2_HOME to your C:\Users<username>.pm2 directory (Win Vista/7/8)
Or take a simple one line patch described in this pull: #982

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment