PM2 executed from within node inherits command line arguments

[stevekeiser]

This is a weird one. Hopefully I can explain clearly. Let's say that I run pm2 start a.js -- 3000 and a.js calls require('child_process').exec('pm2 start b.js -- 4000') then b.js will receive 3000 as it's argument instead of 4000, as expected. This is true even if a.js uses the API, e.g. pm2.start('b.js', {rawArgs: ['--', 4000]}). The child process seems to inherit the command line arguments of the parent.

[catchdave]

I'm having the same problem too. When the parent process is run with command line args, the child processes started via pm2.start() has the arguments (that were specified via pm2.start) ignored and uses the parents arguments instead.

Example:
pm2 start processes.json

processes.json:

{ apps: [
    { name: "loader.js", args: ["--debug", "--path=/var/foo"] }
]}

loader.js

var curProcess = 'foo'; // this comes from somewhere else
var params = {
    name: curProcess,
    rawArgs: ['--', "--bar"]
};
pm2.start('sub-process.js', params);

In the above example, pm2 will start the sub process as pm2 start sub-process.js --debug,--path=/var/foo instead of the expected pm2 start sub-process.js --bar.

Note, I have to use rawArgs here to workaround another pm2 bug specified here: #590

---

It may be worth noting that when this bug occurs, pm2 show X also breaks for the subprocesses with the below error:

Describing process with pid 248 - name ping
undefined:1
--debug,--log-dir=/var/log
 ^
SyntaxError: Unexpected number
at Object.parse (native)
at Object.UX.describeTable (/usr/local/lib/node_modules/pm2/lib/CliUx.js:68:71)
at /usr/local/lib/node_modules/pm2/lib/CLI.js:1140:12
at Array.forEach (native)
at /usr/local/lib/node_modules/pm2/lib/CLI.js:1139:18
at /usr/local/lib/node_modules/pm2/node_modules/pm2-axon-rpc/lib/client.js:45:10
at Parser.<anonymous> (/usr/local/lib/node_modules/pm2/node_modules/pm2-axon/lib/sockets/req.js:67:8)
at Parser.EventEmitter.emit (events.js:95:17)
at Parser._write (/usr/local/lib/node_modules/pm2/node_modules/pm2-axon/node_modules/amp/lib/stream.js:91:16)
at doWrite (_stream_writable.js:226:10)

[catchdave]

@Unitech : Any ideas about this bug?

[Tjatse]

I've confirmed this bug. Just need time to fix it.

[michAtEl]

I've the same problem. It happens only, if the process, that calls pm2.start() is running in pm2. If I start the process, that calls pm2.start(), without pm2, everything works fine.

[mathieumante]

+1
I've the same problem, and also with restart.
Do you have any ideas about this bug?

[jshkurti]

Can you try npm i -g git://github.com/Unitech/PM2#development ?
I think this might have been fixed by https://github.com/Unitech/PM2/pull/1282/files#diff-96936c803a7f9ae2c51530cc944a8cceR324

[Unitech]

Issue fixed since PM2 1.1.3

$ npm install pm2@latest -g
$ pm2 update