pm2 jlist outputs more than json

[aikomastboom]

When running pm2 for the first time:

vagrant@precise64:$ rm -rf .pm2/
vagrant@precise64:$ pm2 jlist -s
Initializing folder for pm2 on /home/vagrant/.pm2
Creating PM2 configuration file in /home/vagrant/.pm2/custom_options.sh
[]

It would be nice if the "Initializing .. options.sh" part would be suppressed as:

• the output is not json anymore and breaks a json parser
• -s is supposed to make it silent but doesn't make it silent enough.

vagrant@precise64:$ rm -rf .pm2/
vagrant@precise64:$ pm2 jlist -s | json_pp
malformed JSON string, neither array, object, number, string or atom, at character offset 0 (before "Initializing folder ...") at /usr/bin/json_pp line 44

[vwal]

Additionally, when the daemon has been killed, on the first run afterwards an object is output from Satan.js in addition to the empty process list, like so:

[root@LOCALDEV:/usr/projects/pm2_nodetest] [02:49 CST]
# pm2 kill 
Daemon killed
[root@LOCALDEV:/usr/projects/pm2_nodetest] [02:49 CST]
# pm2 jlist -s
{ online: true, success: true, pid: 5195 }
[]

Any scripts that expect process list output, but that are not written to handle that initial object will break on the first run. Would it be possible to suppress the initial object, especially with the -s switch?

[aikomastboom]

version 0.8.11

ok:

root:~# pm2 jlist
[{....}]

too silent:

root:~# pm2 jlist -s

too silent:

root:~# pm2 jlist -s --no-daemon

includes non json:

root:~# pm2 jlist --no-daemon
pm2 launched in no-daemon mode (you can add DEBUG="*" env variable to get more messages)
>> pm2 is already daemonized ! You should kill it before launching it in no-daemon mode
[{.....}]

[aikomastboom]

pm2 -V 0.9.2 is still outputting non-json when asked to output json.. please add to 0.9.x roadmap :)

[aikomastboom]

It got a little worse for me, because skipping stdout until first '[' breaks now too. not sure how to workaround this one:

root:~#pm2 jlist --no-daemon
pm2 launched in no-daemon mode (you can add DEBUG="*" env variable to get more messages)
[[[[ PM2/God daemon launched ]]]]
RPC interface [READY] on 6666:localhost
BUS system [READY] on  6667:localhost 
Interaction file does not exists
Error when getting / setting keys { msg: 'secret key is not defined' }
[]

[soyuka]

Fixed here: #627

[aikomastboom]

I applied patch 2734f41 locally to verify.
however the issue is not (completely) resolved for me:

$npm install pm2

$./node_modules/.bin/pm2 jlist
Initializing folder for pm2 on /home/jenkins/.pm2
Creating PM2 configuration file in /home/jenkins/.pm2/custom_options.sh
[]

$./node_modules/.bin/pm2 jlist
[]

$./node_modules/.bin/pm2 jlist --no-daemon
pm2 launched in no-daemon mode (you can add DEBUG="*" env variable to get more messages)
>> pm2 is already daemonized ! You should kill it before launching it in no-daemon mode
[]

[rlidwka]

Initializing folder for pm2 on /home/jenkins/.pm2
Creating PM2 configuration file in /home/jenkins/.pm2/custom_options.sh

This kind of stuff should be in stderr then.

[Unitech]

available in upcoming release