A start job for unit pm2-undefined.service has finished with a failure.
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 43.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
--- PM2 report ----------------------------------------------------------------
Date : Thu Sep 25 2025 13:20:35 GMT-0300 (Brasilia Standard Time)
===============================================================================
--- Daemon -------------------------------------------------
pm2d version : 6.0.13
node version : 18.19.1
node path : /usr/local/bin/pm2
argv : /usr/bin/node,/usr/local/lib/node_modules/pm2/lib/Daemon.js
argv0 : /usr/bin/node
user : undefined
uid : 0
gid : 0
uptime : 15min
===============================================================================
--- CLI ----------------------------------------------------
local pm2 : 6.0.13
node version : 18.19.1
node path : /usr/local/bin/pm2
argv : /usr/bin/node,/usr/local/bin/pm2,report
argv0 : node
user : undefined
uid : 0
gid : 0
===============================================================================
--- System info --------------------------------------------
arch : x64
platform : linux
type : Linux
cpus : 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz
cpus nb : 8
freemem : 16689840128
totalmem : 33370923008
home : /root
===============================================================================
--- PM2 list -----------------------------------------------
┌────┬────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐
│ id │ name │ namespace │ version │ mode │ pid │ uptime │ ↺ │ status │ cpu │ mem │ user │ watching │
├────┼────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤
│ 1 │ api │ default │ 1.0.0 │ fork │ 546 │ 6m │ 0 │ online │ 0.1% │ 70.1mb │ root │ disabled │
└────┴────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘
===============================================================================
--- Daemon logs --------------------------------------------
/root/.pm2/pm2.log last 20 lines:
PM2 | 2025-09-25T13:04:50: PM2 log: Node.js version : 18.19.1
PM2 | 2025-09-25T13:04:50: PM2 log: Current arch : x64
PM2 | 2025-09-25T13:04:50: PM2 log: PM2 home : /root/.pm2
PM2 | 2025-09-25T13:04:50: PM2 log: PM2 PID file : /root/.pm2/pm2.pid
PM2 | 2025-09-25T13:04:50: PM2 log: RPC socket file : /root/.pm2/rpc.sock
PM2 | 2025-09-25T13:04:50: PM2 log: BUS socket file : /root/.pm2/pub.sock
PM2 | 2025-09-25T13:04:50: PM2 log: Application log path : /root/.pm2/logs
PM2 | 2025-09-25T13:04:50: PM2 log: Worker Interval : 30000
PM2 | 2025-09-25T13:04:50: PM2 log: Process dump file : /root/.pm2/dump.pm2
PM2 | 2025-09-25T13:04:50: PM2 log: Concurrent actions : 2
PM2 | 2025-09-25T13:04:50: PM2 log: SIGTERM timeout : 1600
PM2 | 2025-09-25T13:04:50: PM2 log: Runtime Binary : /usr/bin/node
PM2 | 2025-09-25T13:04:50: PM2 log: ===============================================================================
PM2 | 2025-09-25T13:05:06: PM2 log: App [app:0] starting in -fork mode-
PM2 | 2025-09-25T13:05:06: PM2 log: App [app:0] online
PM2 | 2025-09-25T13:11:06: PM2 log: Stopping app:app id:0
PM2 | 2025-09-25T13:11:06: PM2 log: App [app:0] exited with code [0] via signal [SIGINT]
PM2 | 2025-09-25T13:11:07: PM2 log: pid=322 msg=process killed
PM2 | 2025-09-25T13:13:54: PM2 log: App [api:1] starting in -fork mode-
PM2 | 2025-09-25T13:13:54: PM2 log: App [api:1] online
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reported PM2 version, Node.js version, Linux platform, and the daemon log excerpt, focusing on the failed pm2-undefined.service start. Reproduce the service-start failure and trace the reported unit name against PM2's startup behavior; done means the cause is identified and the service starts with the expected unit name.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, linux, node.js
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100