PM2 fails to start Node.js application after server reboot (0 resource usage)

[erich2s]

After server reboot, PM2 shows my Node.js application as "online" but with 0 CPU/memory usage and no actual process running. And I switch to nvm, it works perfectly.

Environment:

• Ubuntu Server 24.04.2
• Node.js 22.16.0 (managed by fnm)
• fnm (latest)
• PM2 (latest)

[zxdong262]

I noticed same issue, I checked the log, it would complain no node in the path, deepseek told me that The symlink is temporary and session-specific—it disappears after logout or reboot.

[justinsvetlik]

Is there a workaround for this?

Edit: I was able to get it working by setting the script attribute in my ecosystem.js to fnm exec --using=[NODE_VERSION] node [PATH_TO_SCRIPT] and the running pm2 start [ECOSYSTEM_FILE] and pm2 save