Connecting to remote PM2

[anthonywebb]

I am having trouble talking to PM2 instances on a remote host. Wondering if someone could help set me straight.

I have set up an env variable called: PM2_BIND_ADDR [root@cp-bus-api app]# echo $PM2_BIND_ADDR 0.0.0.0

But when I start PM2 there is nothing on port 6666 [root@cp-bus-api app]# netstat -an Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN

I am running the latest version of PM2: [root@cp-bus-api app]# pm2 -v 0.11.0

Once I actually have something running on port 6666 I assume I will need to configure the firewall to let my PM2-web server to see it. I'm just not having much luck getting pm2 to actually open up and start doing something on that port.

[achingbrain]

I think this is related to #28 - when pm2 introduced unix sockets for it's message bus a couple of weeks ago it didn't retain any functionality for remote connections, only local to the machine, which explains why nothing is listening on port 6666.

[achingbrain]

Looking at bit deeper at the changes in the recent pm2 release, I'm not sure this will ever work again unless the pm2 maintainers add explicit support for it.

I suppose you could socat the socket to a tcp port outside of pm2, but that would invalidate their security model.

[anthonywebb]

This is a real bummer, love the project, here's hoping the PM2 guys will come around

[achingbrain]

Indeed, the monitoring-multiple-hosts thing was kind of why I wrote pm2-web in the first place.

[dbuarque]

+1

[cmnstmntmn]

any updates on this?

[hulu1522]

@achingbrain Is it possible for the pm2-web application to open a TCP socket and return data from pm2. It would be like a middle-man setup but that way those of us wanting remote monitoring of internal PM2 apps can get the information we need. Thanks.

[scniro]

+1