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
I want to preface this minor issue by saying this minor display bug did not break the install in any way the application and pm2 are working fine.
Description
After fresh global install of pm2 and n8n I noticed pm2 list shows the wrong version for n8n. So after reinstalling PM2 or clearing its cache, pm2 list loses default columns (namespace, version, pid, uptime, user, watching) and shows a reduced set (id, name, mode, ↺, status, cpu, memory). It also reports the wrong version for a globally installed app (n8n), showing nvm’s version (0.40.1) instead of n8n’s (1.81.4).
Preface
I want to preface this minor issue by saying this minor
display
bug did not break the install in any way the application and pm2 are working fine.Description
After fresh global install of pm2 and n8n I noticed
pm2 list
shows the wrong version for n8n. So after reinstalling PM2 or clearing its cache,pm2 list
loses default columns (namespace
,version
,pid
,uptime
,user
,watching
) and shows a reduced set (id
,name
,mode
,↺
,status
,cpu
,memory
). It also reports the wrong version for a globally installed app (n8n), showing nvm’s version (0.40.1
) instead of n8n’s (1.81.4
).Steps to Reproduce
0.40.1
and Node.js22.14.0
npm install -g n8n
(version 1.81.4)ecosystem.config.js
:5.Start: cd /home/user/.n8n && pm2 start ecosystem.config.js.
6.Check: pm2 list—shows full columns with version: 0.40.1.
7.Reset: pm2 kill && rm -rf ~/.pm2/* && cd /home/user/.n8n && pm2 start ecosystem.config.js.
8.Check again: pm2 list—missing columns, version gone or 0.40.1 in pm2 show n8n.
Expected Behavior
Actual Behavior
Outputs
Environment:
Attempts to Fix
pm2 delete n8n && pm2 start ecosystem.config.js
pm2 kill && rm -rf ~/.pm2/* && pm2 start ecosystem.config.js
Reinstall PM2: npm uninstall -g pm2 && npm install -g pm2@latest
The text was updated successfully, but these errors were encountered: