Pm2: How to disable log message "Unknown id _old_1"?

Created on 21 Apr 2018  路  9Comments  路  Source: Unitech/pm2

What's going wrong?

My log PM2. Every second "Unknown id _old_1"

30703622-e689e0f6-9ef8-11e7-88a6-1cc92724f041

I have log files of 3GB. How to disable log message "Unknown id _old_1"?

30704042-140c254c-9efa-11e7-87d5-97a8658a96a3

How could we reproduce this issue?

I do not know, maybe after the restart.

Supporting information

$ pm2 report
===============================================================================
--- PM2 REPORT (Sat Apr 21 2018 17:17:51 GMT+0300 (MSK)) ----------------------
===============================================================================
--- Daemon -------------------------------------------------
pm2d version         : 2.10.2
node version         : 8.11.1
node path            : /usr/bin/pm2
argv                 : /usr/bin/node,/usr/lib/node_modules/pm2/lib/Daemon.js
argv0                : node
user                 : undefined
uid                  : 0
gid                  : 0
uptime               : 36min
===============================================================================
--- CLI ----------------------------------------------------
local pm2            : 2.10.2
node version         : 8.11.1
node path            : /usr/bin/pm2
argv                 : /usr/bin/node,/usr/bin/pm2,report
argv0                : node
user                 : root
uid                  : 0
gid                  : 0
===============================================================================
--- System info --------------------------------------------
arch                 : x64
platform             : linux
type                 : Linux
cpus                 : Intel(R) Xeon(R) CPU D-1531 @ 2.20GHz
cpus nb              : 6
freemem              : 6739058688
totalmem             : 8363978752
home                 : /root
===============================================================================
stale

Most helpful comment

pm2 kill took care of the dead process

https://github.com/Unitech/pm2/issues/2028

All 9 comments

I got the same issue.

pm2 kill took care of the dead process

https://github.com/Unitech/pm2/issues/2028

pm2 kill works , but kills all process

I'm having this problem since updating to version 4. The only solution is to do this: pm2 kill && pm2 resurrect

I've set up a cron job that runs this every hour and that so far "solved" the problem. Hopefully, there is a fix soon

p5bsfQe

PM2 version : 4.1.2
Node.js version : 10.16.3
Current arch : x64

pm2 kill && pm2 resurrect

Thanks this fixed it for me when nothing else would.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

PM2 version : 4.1.2
Node.js version : 10.16.3
Current arch : x64

We have the same problem.

Was this page helpful?
0 / 5 - 0 ratings