gistfile1.txt

Starting infinite loop tests
  pm2:satan [PING PM2] Trying to connect to server +0ms
  pm2:satan Daemon not launched +111ms
  pm2:satan PM2 alive: false +2ms
  pm2:satan Launching daemon +0ms
  pm2:satan PM2 Daemon launched +344ms { online: true, success: true, pid: 6262, pm2_version: '0.10.4' }
  pm2:interface:daemon [PING INTERACTOR] Trying to connect to Interactor daemon +4ms
  pm2:interface:daemon Interactor Daemon not launched +102ms
  pm2:interface:daemon Interactor offline, launching it... +0ms
  pm2:interface:daemon Waiting for message +6ms
  pm2:interface:daemon Interactor ready +236ms
[Keymetrics.io] Launched - Log: /home/travis/.pm2/agent.log | Conf: /home/travis/.pm2/agent.json | PID: /home/travis/.pm2/agent.pid
  pm2:satan Launching RPC client on port 6666 localhost +122ms
  pm2:satan Connected to Daemon +3ms
  pm2:cli Got message from Satan as succesfully connected to PM2, now parsing arguments +5ms
[PM2] [WARNING]  you're using the 0.10.x node version, it's prefered that you switch to fork mode by adding the -x parameter. 0.11.x can use cluster_mode (default mode) efficiently.
  pm2:satan Calling daemon method pm2:findByFullPath +2ms
  pm2:satan Calling daemon method pm2:prepare +8ms
[PM2] Process killtoofast.js launched
  pm2:monit Getting interaction info +110ms
  pm2:interface:daemon [PING INTERACTOR] Trying to connect to Interactor daemon +0ms
  pm2:interface:daemon Interactor Daemon alive +1ms
  pm2:interface:daemon Ping socket closed +0ms
  pm2:interface:daemon Generating methods +0ms
  pm2:interface:daemon +-- Creating kill method +5ms
  pm2:interface:daemon +-- Creating getInfos method +0ms
  pm2:interface:daemon Methods generated +0ms
  pm2:interface:daemon Closing RPC INTERACTOR +3ms
  pm2:interface:daemon RPC INTERACTOR cleanly closed +0ms
  pm2:satan Calling daemon method pm2:getMonitorData +1ms
● Agent online - public key: XXXP3 - machine name: testing-worker-linux-11-1-1899-linux-18-33932066 - Web access: http://app.keymetrics.io/
┌──────────────────┬────┬─────────┬──────┬────────┬───────────┬────────┬────────┬─────────────┐
│ App name         │ id │ mode    │ PID  │ status │ restarted │ uptime │ memory │    watching │
├──────────────────┼────┼─────────┼──────┼────────┼───────────┼────────┼────────┼─────────────┤
│ unstable-process │ 0  │ cluster │ 6274 │ online │         0 │ 0s     │ 0 B    │ unactivated │
└──────────────────┴────┴─────────┴──────┴────────┴───────────┴────────┴────────┴─────────────┘
 Use `pm2 desc[ribe] <id>` to get more details
  pm2:satan Disconnecting PM2 RPC +68ms
  pm2:interface:daemon Socket being closed +0ms
  pm2:satan PM2 RPC closed +0ms
Waiting for process to restart too many times and pm2 to stop it...................................................  pm2:satan [PING PM2] Trying to connect to server +0ms
  pm2:satan Daemon alive +9ms
  pm2:satan PM2 alive: true +1ms
  pm2:satan Launching RPC client on port 6666 localhost +0ms
  pm2:satan Connected to Daemon +2ms
  pm2:cli Got message from Satan as succesfully connected to PM2, now parsing arguments +5ms
  pm2:satan Calling daemon method pm2:getMonitorData +1ms