Unitech / Unitech/pm2

Not able to link pm2.io

Open
#5,841 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
43.3k
Forks
2.7k
PR merge metrics
No merged PRs in 30d

Description

What's going wrong?

Not able to connect server pm2 console to pm2.io monitors.

--- PM2 report ----------------------------------------------------------------
Date : Fri Jun 07 2024 08:06:51 GMT+0000 (Coordinated Universal Time)

--- Daemon -------------------------------------------------
pm2d version : 5.4.0
node version : 12.22.1
node path : /home/apps/.nvm/versions/node/v12.22.1/bin/pm2
argv : /home/apps/.nvm/versions/node/v12.22.1/bin/node,/home/apps/.nvm/versions/node/v12.22.1/lib/node_modules/pm2/lib/Daemon.js
argv0 : node
user : apps
uid : 1001
gid : 1002
uptime : 11min

--- CLI ----------------------------------------------------
local pm2 : 5.4.0
node version : 12.22.1
node path : /home/apps/.nvm/versions/node/v12.22.1/bin/pm2
argv : /home/apps/.nvm/versions/node/v12.22.1/bin/node,/home/apps/.nvm/versions/node/v12.22.1/bin/pm2,report
argv0 : node
user : apps
uid : 1001
gid : 1002

--- System info --------------------------------------------
arch : x64
platform : linux
type : Linux
cpus : Intel(R) Xeon(R) CPU @ 3.10GHz
cpus nb : 4
freemem : 10051145728
totalmem : 16783462400
home : /home/apps

--- PM2 list -----------------------------------------------
┌────┬────────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐
│ id │ name │ namespace │ version │ mode │ pid │ uptime │ ↺ │ status │ cpu │ mem │ user │ watching │
├────┼────────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤
│ 1 │ nextjs │ default │ 0.39.1 │ fork │ 14808 │ 10m │ 1 │ online │ 0% │ 44.1mb │ apps │ disabled │
│ 0 │ wbs-api │ default │ N/A │ fork │ 14794 │ 10m │ 1 │ online │ 0% │ 123.2mb │ apps │ disabled │
└────┴────────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘

--- Daemon logs --------------------------------------------
/home/apps/.pm2/pm2.log last 20 lines:
PM2 | 2024-06-07T07:55:18: PM2 log: Application log path : /home/apps/.pm2/logs
PM2 | 2024-06-07T07:55:18: PM2 log: Worker Interval : 30000
PM2 | 2024-06-07T07:55:18: PM2 log: Process dump file : /home/apps/.pm2/dump.pm2
PM2 | 2024-06-07T07:55:18: PM2 log: Concurrent actions : 2
PM2 | 2024-06-07T07:55:18: PM2 log: SIGTERM timeout : 1600
PM2 | 2024-06-07T07:55:18: PM2 log: ===============================================================================
PM2 | 2024-06-07T07:55:18: PM2 log: App [wbs-api:0] starting in -fork mode-
PM2 | 2024-06-07T07:55:18: PM2 log: App [nextjs:1] starting in -fork mode-
PM2 | 2024-06-07T07:55:18: PM2 log: App [wbs-api:0] online
PM2 | 2024-06-07T07:55:18: PM2 log: App [nextjs:1] online
PM2 | 2024-06-07T07:56:45: PM2 log: Stopping app:wbs-api id:0
PM2 | 2024-06-07T07:56:45: PM2 log: App [wbs-api:0] exited with code [0] via signal [SIGINT]
PM2 | 2024-06-07T07:56:45: PM2 log: pid=14694 msg=process killed
PM2 | 2024-06-07T07:56:45: PM2 log: App [wbs-api:0] starting in -fork mode-
PM2 | 2024-06-07T07:56:45: PM2 log: App [wbs-api:0] online
PM2 | 2024-06-07T07:56:45: PM2 log: Stopping app:nextjs id:1
PM2 | 2024-06-07T07:56:45: PM2 log: App [nextjs:1] exited with code [0] via signal [SIGINT]
PM2 | 2024-06-07T07:56:45: PM2 log: pid=14700 msg=process killed
PM2 | 2024-06-07T07:56:45: PM2 log: App [nextjs:1] starting in -fork mode-
PM2 | 2024-06-07T07:56:45: PM2 log: App [nextjs:1] online

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is named. Start by reproducing the pm2.io connection failure with the supplied PM2 5.4.0, Node.js 12.22.1, Linux, and daemon-log context, then trace the CLI and daemon behavior involved in linking. Done means the cause is isolated and the connection to pm2.io monitors works reliably.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
devops, observability
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.