Skip to content
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

not working at all #131

Closed
gergokoos opened this issue Oct 26, 2013 · 5 comments
Closed

not working at all #131

gergokoos opened this issue Oct 26, 2013 · 5 comments

Comments

@gergokoos
Copy link

Hello,

I followed the instructions to install pm2, but it fails to do anything.

installation:
sudo npm install pm2 -g

trying to do something:
pm2 -V
{ online: true, success: true, pid: 17908 }

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 net.js:1135:9
at asyncCallback (dns.js:68:16)
at Object.onanswer as oncomplete

(at this point I have to press ctrl-c to exit)

node version:
node -v
v0.10.21

uname -a
Linux example.com 3.2.0-4-amd64 #1 SMP Debian 3.2.41-2+deb7u2 x86_64 GNU/Linux

@Unitech
Copy link
Owner

Unitech commented Oct 27, 2013

Error: listen EADDRINUSE

You have an app listening to 6666 or 6667

@Unitech Unitech closed this as completed Oct 27, 2013
@gergokoos
Copy link
Author

so, if anyone encounter this problem again, here is how to fix it:
go to pm2 folder (in case of global install: /usr/local/lib/node_modules/pm2)
edit constants.js where the port is, and be happy running it next to your irc server.
(as the comment says on top of the constants.js, it can broke the interface or something else)

@Emerson
Copy link

Emerson commented Oct 21, 2014

Seeing this error as well. No idea how to fix it.

@derek-watson
Copy link

As a temporary workaround, set pm2's RCP ports to something else at runtime:

PM2_RPC_PORT=9666 PM2_PUB_PORT=9667 pm2 ...

@Emerson
Copy link

Emerson commented Dec 2, 2014

After discussing this with @derek-watson it turns out that my ~/.pm2 folder had permission issues. I deleted the entire folder and was able to use pm2 again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants