I keep getting this everytime I try to start with pm2

[chrisfranko]

[wsc] =✓= The socket connection has been established.
node-app-0 [eth] =i= { id: 'lyylNycDev1',
node-app-0 stats:
node-app-0 { active: true,
node-app-0 syncing: false,
node-app-0 mining: false,
node-app-0 hashrate: 0,
node-app-0 peers: 0,
node-app-0 gasPrice: '20000000000',
node-app-0 uptime: 100 } }
node-app-0 [eth] =✘= TypeError: results.reverse is not a function
node-app-0 at /root/eth-net-intelligence-api/lib/node.js:622:21
node-app-0 at /root/eth-net-intelligence-api/node_modules/async/lib/async.js:52:16
node-app-0 at /root/eth-net-intelligence-api/node_modules/async/lib/async.js:361:13
node-app-0 at /root/eth-net-intelligence-api/node_modules/async/lib/async.js:52:16
node-app-0 at iterate (/root/eth-net-intelligence-api/node_modules/async/lib/async.js:260:24)
node-app-0 at async.forEachOfSeries.async.eachOfSeries (/root/eth-net-intelligence-api/node_modules/async/lib/async.js:281:9)
node-app-0 at _asyncMap (/root/eth-net-intelligence-api/node_modules/async/lib/async.js:355:9)
node-app-0 at Object.mapSeries (/root/eth-net-intelligence-api/node_modules/async/lib/async.js:347:20)
node-app-0 at Node.getHistory (/root/eth-net-intelligence-api/lib/node.js:601:8)
node-app-0 at Primus. (/root/eth-net-intelligence-api/lib/node.js:246:8)

[lgn21st]

I have same problem as well.

[alanchchen]

I have the same problem, too.

I run this with pm2 in different docker containers.
One have the same problem but the other does not.
Same node.js version, same Dockerfile.

I didn't see this problem after restarting my eth-netstats server.

[Arachnid]

Same problem here; perhaps it's related to some changes in recent web3 or geth? Restarting doesn't seem to help.

[mpitid]

It has to do with the history range requested by eth-netstats. The crash should be addressed by #242