[PM2] Spawning PM2 daemon with pm2_home/root/.pm2

[Morgan-Moon]

What's going wrong?

Regardless of what command I enter, I get the same output from pm2 "[PM2] Spawning PM2 daemon with pm2_home/root/.pm2"

I've tried rebooting my VPS, uninstalling pm2 and installing it with a different package manager npm I -> yarn add.

pm2 start: Sends console response [PM2] Spawning PM2 daemon with pm2_home/root/.pm2 and then does nothing, until I manually cancel the process.

How could we reproduce this issue?

I am not 100% sure, it was working perfectly fine yesterday, then today, when I went to enter the command "pm2 restart 0" along came this issue

Supporting information

pm2 Version: v5.4.2 node Version v20.15.1 npm Version: v10.7.0 yarn Version: 1.22.22 Ubuntu Version: 22.04.4 LTS

# Run the following commands
$ pm2 report
> [PM2] Spawning PM2 daemon with pm2_home/root/.pm2

pm2 list does nothing until I have to cancel the operation manually

[MustagheesButt]

Facing a similar issue on Debian 12, pm2 5.4.2. Every pm2 command shows the following output, and then it doesn't exit:

[PM2] Spawning PM2 daemon with pm2_home=/home/myuser/.pm2
[PM2] PM2 Successfully daemonized

And after a while the VPS dies because of high memory usage. Turns out pm2 is spawning tons of update processes

ps aux | grep pm2
myuser     2997  0.1  2.0 621176 63628 ?        Ssl  12:33   0:00 node /usr/local/bin/pm2 update
myuser     3018  0.1  2.0 621184 62692 ?        Ssl  12:33   0:00 node /usr/local/bin/pm2 update
...

If I set ulimit before running a pm2 command then I can stop my VPS from becoming unresponsive.

Was working fine till today. Tried reinstalling pm2 using npm still no luck.

Edit: Just restored a backup from several days ago, and pm2 is working but version 5.3.1, no idea how it got upgraded to latest.