You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While stopping a pm2 --no-daemon process it prints some console message, one of them prints %s directly without putting process name in it.
[Watch] Process name %s is being stopped so I won't restart it
How could we reproduce this issue?
Start any nodejs script with pm2 start app.js --watch --no-daemon , and then stop it by sending CTRL + C Signal.
Supporting information
18:19:32 PM2 | pm2 has been killed by signal, dumping process list before exit...
18:19:32 PM2 | Deleting process 0
18:19:32 PM2 | Stopping app:app id:0
2018-06-25 18:19:32: App [app] with id [0] and pid [88962], exited with code [0] via signal [SIGINT]
18:19:32 PM2 | App [app] with id [0] and pid [88962], exited with code [0] via signal [SIGINT]
2018-06-25 18:19:32: Change detected on path newrelic_agent.log for app app - restarting
2018-06-25 18:19:32: [Watch] Process name %s is being stopped so I won't restart it
18:19:32 PM2 | Change detected on path newrelic_agent.log for app app - restarting
18:19:32 PM2 | [Watch] Process name %s is being stopped so I won't restart it
2018-06-25 18:19:32: pid=88962 msg=process killed
2018-06-25 18:19:32: [PM2] Exited peacefully
$ pm2 report
The text was updated successfully, but these errors were encountered:
vivex
pushed a commit
to vivex/pm2
that referenced
this issue
Jun 25, 2018
What's going wrong?
While stopping a pm2 --no-daemon process it prints some console message, one of them prints
%s
directly without putting process name in it.How could we reproduce this issue?
Start any nodejs script with
pm2 start app.js --watch --no-daemon
, and then stop it by sending CTRL + C Signal.Supporting information
The text was updated successfully, but these errors were encountered: