Ecossystem and node --inspect

What's going wrong?

I've created a new ecosystem.config.js where I've placed all my nodejs apps.

The node_args --inspect parameter is being ignored.

Running ps aux | grep node returns the following:

node /Users/vmagalhaes/gyant/backend/gyant-diagnosis/src/server.js

If I call pm2 start src/server.js --node-args="--inspect" then it works as expected.

Supporting information

--- PM2 report ----------------------------------------------------------------
Date                 : Thu May 28 2020 14:43:45 GMT+0100 (Western European Summer Time)
===============================================================================
--- Daemon -------------------------------------------------
pm2d version         : 4.4.0
node version         : 10.15.3
node path            : /Users/vmagalhaes/.nvm/versions/node/v10.15.3/bin/node
argv                 : /Users/vmagalhaes/.nvm/versions/node/v10.15.3/bin/node,/Users/vmagalhaes/.nvm/versions/node/v10.15.3/lib/node_modules/pm2/lib/Daemon.js
argv0                : node
user                 : vmagalhaes
uid                  : 501
gid                  : 20
uptime               : 244min
===============================================================================
--- CLI ----------------------------------------------------
local pm2            : 4.4.0
node version         : 10.15.3
node path            : /Users/vmagalhaes/.nvm/versions/node/v10.15.3/bin/pm2
argv                 : /Users/vmagalhaes/.nvm/versions/node/v10.15.3/bin/node,/Users/vmagalhaes/.nvm/versions/node/v10.15.3/bin/pm2,report
argv0                : node
user                 : vmagalhaes
uid                  : 501
gid                  : 20
===============================================================================
--- System info --------------------------------------------
arch                 : x64
platform             : darwin
type                 : Darwin
cpus                 : Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz
cpus nb              : 12
freemem              : 470261760
totalmem             : 17179869184
home                 : /Users/vmagalhaes
===============================================================================
--- PM2 list -----------------------------------------------
┌─────┬─────────────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐
│ id  │ name            │ namespace   │ version │ mode    │ pid      │ uptime │ ↺    │ status    │ cpu      │ mem      │ user     │ watching │
├─────┼─────────────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤
│ 3   │ connector       │ default     │ 0.6.5   │ fork    │ 99588    │ 3h     │ 0    │ online    │ 0%       │ 32.9mb   │ vma… │ enabled  │
│ 1   │ conversation    │ default     │ 1.0.0   │ fork    │ 99555    │ 3h     │ 0    │ online    │ 0%       │ 30.2mb   │ vma… │ enabled  │
│ 6   │ diagnosis       │ default     │ 1.0.0   │ fork    │ 99637    │ 3h     │ 0    │ online    │ 0%       │ 28.6mb   │ vma… │ enabled  │
│ 5   │ extractor       │ default     │ 0.0.1   │ fork    │ 99622    │ 3h     │ 0    │ online    │ 0%       │ 30.9mb   │ vma… │ enabled  │
│ 8   │ ng-admin        │ default     │ 0.0.1   │ fork    │ 99695    │ 3h     │ 0    │ online    │ 0%       │ 29.6mb   │ vma… │ enabled  │
│ 7   │ nlp             │ default     │ N/A     │ fork    │ 99661    │ 3h     │ 0    │ online    │ 0%       │ 24.6mb   │ vma… │ enabled  │
│ 4   │ reasoning       │ default     │ 0.0.1   │ fork    │ 99604    │ 3h     │ 0    │ online    │ 0%       │ 32.3mb   │ vma… │ enabled  │
│ 2   │ web-frontend    │ default     │ 1.0.0   │ fork    │ 50954    │ 35m    │ 4    │ online    │ 0%       │ 68.5mb   │ vma… │ enabled  │
│ 0   │ webauth         │ default     │ 1.0.0   │ fork    │ 99552    │ 3h     │ 0    │ online    │ 0%       │ 29.3mb   │ vma… │ enabled  │
└─────┴─────────────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘
===============================================================================
--- Daemon logs --------------------------------------------
/Users/vmagalhaes/.pm2/pm2.log last 20 lines:
PM2        | 2020-05-28T14:07:45: PM2 log: App [web-frontend:2] online
PM2        | 2020-05-28T14:07:45: PM2 log: Change detected on path .git/logs/refs/remotes/origin/OSFFD-123 for app web-frontend - restarting
PM2        | 2020-05-28T14:07:45: PM2 log: Stopping app:web-frontend id:2
PM2        | 2020-05-28T14:07:45: PM2 log: App [web-frontend:2] exited with code [0] via signal [SIGINT]
PM2        | 2020-05-28T14:07:45: PM2 error: Cancelling versioning data parsing
PM2        | 2020-05-28T14:07:45: PM2 log: pid=50719 msg=process killed
PM2        | 2020-05-28T14:07:45: PM2 log: App [web-frontend:2] starting in -fork mode-
PM2        | 2020-05-28T14:07:45: PM2 log: App [web-frontend:2] online
PM2        | 2020-05-28T14:07:54: PM2 log: Change detected on path .git/index for app web-frontend - restarting
PM2        | 2020-05-28T14:07:54: PM2 log: Stopping app:web-frontend id:2
PM2        | 2020-05-28T14:07:54: PM2 log: pid=50754 msg=failed to kill - retrying in 100ms
PM2        | 2020-05-28T14:07:54: PM2 log: pid=50754 msg=failed to kill - retrying in 100ms
PM2        | 2020-05-28T14:07:54: PM2 log: pid=50754 msg=failed to kill - retrying in 100ms
PM2        | 2020-05-28T14:07:54: PM2 log: pid=50754 msg=failed to kill - retrying in 100ms
PM2        | 2020-05-28T14:07:55: PM2 log: pid=50754 msg=failed to kill - retrying in 100ms
PM2        | 2020-05-28T14:07:55: PM2 log: pid=50754 msg=failed to kill - retrying in 100ms
PM2        | 2020-05-28T14:07:55: PM2 log: App [web-frontend:2] exited with code [0] via signal [SIGINT]
PM2        | 2020-05-28T14:07:55: PM2 log: pid=50754 msg=process killed
PM2        | 2020-05-28T14:07:55: PM2 log: App [web-frontend:2] starting in -fork mode-
PM2        | 2020-05-28T14:07:55: PM2 log: App [web-frontend:2] online

The report identifies ecosystem.config.js and the CLI --node-args="--inspect" path; start by reproducing both launches and compare the ps aux | grep node output. Done means the ecosystem configuration passes --inspect to the Node.js process just as the CLI invocation does.