pm2 module does not detect running node about eth-netstats HOT 4 CLOSED

Would need to see the error log to see the problem. You might try reading the pm2 docs to understand the software you are attempting to utilize

http://pm2.keymetrics.io/docs/usage/quick-start/

This Issue tracker is for bugs, not help desk requests

from eth-netstats.

Sorry mikeyb, I tried every possible way to set everything up as discribed in the different wiki and READMEs around, but couldn't resolve this.

It appears the problem is with pm2 not properly connecting:

2018-02-22 18:48 +01:00: [wsc] =✘= Socket error: { Error: connect ECONNREFUSED 127.0.0.1:3000
    at Object._errnoException (util.js:1003:13)
    at _exceptionWithHostPort (util.js:1024:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1195:14)
  errno: 'ECONNREFUSED',
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '127.0.0.1',
  port: 3000,
  type: 'error',
  target: 
   WebSocket {
     domain: null,
     _events: { error: [Function: onerror] },
     _eventsCount: 1,
     _maxListeners: undefined,
     _socket: null,
     _ultron: null,
     _closeReceived: false,
     bytesReceived: 0,
     readyState: 3,
     supports: { binary: true },
     extensions: null,
     _binaryType: 'arraybuffer',
     _isServer: false,
     url: 'ws://localhost:3000/api/?_primuscb=M6-eNQn',
     protocolVersion: 13,
     _closeTimer: null,
     _closeCode: 1006 } }

I will look into it further. Still some help would be awesome. Maybe more user trying to set netstats up have this problem, so it would be worth discussing it here and fix the issue behind it :)

from eth-netstats.

You might check closed issues, but this error is stating that you don't have anything running on port 3000 via localhost. So some dependency is not running, or there is a firewall blocking access to localhost port 3000

from eth-netstats.

Thanks for the advice. I did not know pm2 that well. Apparently this package expects an open port to connect to. I thought it would open the port itself.
I resolved this issue by running eth-netstats before starting the eth-net-intelligence-api.

I guess everyone with more experience would have known this. But maybe there should be a hint in the README or wiki, stating in which order to execute the different parts?

from eth-netstats.