Open ouraios opened 3 years ago
Same here. Since the last update, pm2 ls
always shows cpu 0%.
But, if you type pm2 reset 99
, the same table is shown with the correct value. So right now I'm using reset to see cpu usage.
I put "99" because it doesn't exists, so you will see Error: 99 id unkown, but the table will be shown anyway, without resetting anything.
I hope this issue is fixed soon.
Hi, it's still here in version 4.5.6
Any thoughts when it would be fixed?
Hi its still here in pm2 version 5.2.2 ubuntu 22.04 npm 6.14.17 node v14.21.1
Will this be fixed?
But, if you type
pm2 reset 99
, the same table is shown with the correct value. So right now I'm using reset to see cpu usage.
Thanks @JAlbertoGonzalez this helped me
Same here
Bit off topic, sorry in advance:
But even Angular compiler process shows up with a max of 50MB memory usage, and for sure its a lot more. Anyone has the same problem with Mem: XXX usage instead of CPU, showing way to low value and never changing?
But other (NX) apps also never go above 50MB memory usage.. So it seems like PM2 is creating a fork or something, and only reads the parent cpu/memory usage.. Thats the feeling I get with this CPU/MEM issue
Thanks
Same here
same issue here with node@18.19.1
and pm2@5.3.1
Almost 4-year old issue, pm2 reset 999
is the only solution to properly show CPU usage. Wow.
What's going wrong?
After updating to last pm2 version command
pm2 ls
display cpu at 0% usage but commandpm2 monit
display real cpu usage for ~30-40%I use pm2-metrics which collect the 0% cpu from
pm2 ls
apparently.How could we reproduce this issue?
Good question i dont know, for me it happened after updating pm2 to last version.
Supporting information